|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
INPROC Sample: Demonstrates an In-Process Automation Server Application
INPROC is an in-process Automation server. Unlike the other Automation server samples provided, INPROC can be loaded as a dynamic-link library (DLL) in the client's address space. This sample uses the native compiler COM support. See the MFC INPROC sample for more information.
Building and Running the Sample
To build and run this sample
- Open the solution inproc.sln.
- On the Build menu, click Build Solution.
- Register the server:
- Change the path in server\inproc.reg to the path of the inproc.dll you just built.
- Set the ipdrive project as the startup project (right-click the project node and click Set as StartUp Project) and run this application.
Comparison with the MFC Version
The differences between this sample and the MFC sample with the same name are:
- The COleDispatchDriver class is no longer necessary. Instead, #import is used to import a type library.
- The _bstr_t and _variant_t wrapper classes are used to simplify operations of BSTR and VARIANT types.
- __declspec(property) is used to simplify assignment operations for properties of COM objects.
- COM error handling is now performed by using the _com_error class.
With the Visual C++ native compiler COM support, the resulting sample code is shorter and more efficient. The MFC-based INPROC sample uses dispinterfaces only. Compare this sample with the MFC version to see the differences in source code.
This sample demonstrates the following keywords:
dispinterface; #import; _com_ptr_t; _variant_t; _bstr_t; _com_error