This module discussed the role played by development frameworks, namely ATL and MFC. We also looked at core ATL classes. We generated an in-process server using the ATL COM AppWizard. We added a COM object and studied ATL code and files.
We designed properties and methods for our COM object and its interfaces. We added a constant and data structure directly to the IDL file. Finally, we used several modules to implement properties, methods, and internal data within our COM object implementation.
We will develop a client that uses our COM object in the next module.
The Server location is the next step involved in the COM object life-cycle process. In this step,
COM locates the object implementation and initiates a server process for the object.
A special component called Service Control Manager (SCM) is responsible for the location and execution of the COM server that implements the COM object. The SCM ensures that when a
client request is made, the appropriate server is connected and ready to receive the request. The SCM stores all the class information in the system registry, under a special text key named with the object's CLSID.
For example, SCM stores the file pathnames of the COM servers, which helps for their localization. The COM client obtains this information through the COM library. This is the basis for the Server location step.
