The Anatomy of a COM Server

  • Andrew Troelsen


In terms of software longevity, Microsoft’s Component Object Model (COM) has enjoyed a lengthy and successful life. Formally solidified circa 1993, COM formalized a specific process for building reusable, binary software components. When developers abide by the rules of COM, they are presented with a number of desirable byproducts. One of the great byproducts of COM components is their language-independent nature. This trait allows software developers to build COM servers in one language (such as VB 6.0) and reuse them in any number of other COM-aware languages (such as C++). However, depending on your programming tool of choice, the internal composition of a COM server may be a bit of a mystery.


Type Information Class Factory Library Function Object User Custom Interface 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Andrew Troelsen 2002

Authors and Affiliations

  • Andrew Troelsen

There are no affiliations available

Personalised recommendations