CComModule Replacement Classes
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
Earlier versions of ATL used CComModule. In ATL 7.0 and later, CComModule functionality is replaced by several classes.
This separation makes the functionality in CComModule more granular, creating separate classes to provide support for COM, windowing, interface debugging, and application-specific (DLL or EXE) features.
In addition, Init and Term methods have moved into the constructors and destructors for the module classes; there is no longer a need to call Init and Term.
The following table describes the classes that replace CComModule.
| Class | Description |
|---|---|
CAtlBaseModule |
Contains information required by most applications that use ATL. Contains the HINSTANCE of the module and the resource instance. |
CAtlComModule |
Contains information required by the COM classes in ATL. |
CAtlWinModule |
Contains information required by the windowing classes in ATL. |
CAtlDebugInterfacesModule |
Contains support for interface debugging. |
CAtlModule |
The following CAtlModule-derived classes are customized to contain information required in a particular application type. Most members in these classes can be overridden:
CAtlDllModuleT Provides code for the standard exports.
CAtlExeModuleT Provides code required in an EXE.
|
CComModule is still available for backward compatibility.