Component Services Overview
The Component Services feature for Microsoft® Windows® CE .NET is a platform-independent object-oriented system for creating binary software components that can interact with other Component Object Model (COM)-based components in the same process space, in other processes, or on remote computers.
The following levels of run-time support for COM-based applications are supported:
- Minimal COM provides a baseline API set for COM object creation. This feature requires about 10–20K of memory. This feature is only available in the headless configurations.
- COM provides a midrange implementation of COM and Automation that supports only in-process free-threaded objects. This feature requires about 100–200K of memory.
- The Distributed Component Object Model (DCOM) provides a full-featured COM implementation equivalent to Microsoft Windows NT® 4.0 SP5 and requires more than 700K of memory.
In addition, you can add storage functionality to any one of the three COM features by selecting COM Storage from the Catalog.
Feature Summary
The following table shows operating system design information for Component Services.
| Element | Information |
|---|---|
| Dependencies | None |
| Hardware considerations | None |
Modules and Components
The following table shows the components and modules that implement Component Services.
| Item | Module | Component |
|---|---|---|
| Minimal COM | uuid, ole32, oleaut32, mcombase, mcommem, mcomstr, mcommon, mcomlib, ole232, docfile, msf, exp | None |
| COM | uuid, ole32, oleaut32, ole232, com, docfile, msf, exp | None |
| DCOM | dllhost, dcomssd, rpcrt4, rpcltccm, rpcltscm, ole32, oleaut32, uuid, dcomole, idisproxy | None |
| COM Storage | stg or mcomstm depending on the previous COM choices | None |
Application Development Topics
Component Services (COM and DCOM)
Creating and Initializing COM Objects
See Also
Component Services Implementation Considerations
Last updated on Friday, April 09, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.