Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 574 views

    Com, Dcom, Com+

    Uploaded by

    Peter R. Egli
    Overview of Microsoft COM / DCOM technology. DCOM is Microsoft's component technology and can be roughly compared to CORBA technology. DCOM is however tightly bound to the Windows operating system (Win32 API). Windows Runtime is a newer Microsoft technology that borrows much of the concepts of COM/DCOM.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    Com, Dcom, Com+

    Uploaded by

    Peter R. Egli
    574 views20 pages
    Overview of Microsoft COM / DCOM technology. DCOM is Microsoft's component technology and can be roughly compared to CORBA technology. DCOM is however tightly bound to the Windows operating system (Win32 API). Windows Runtime is a newer Microsoft technology that borrows much of the concepts of COM/DCOM.

    Original Title

    COM, DCOM, COM+

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Overview of Microsoft COM / DCOM technology. DCOM is Microsoft's component technology and can be roughly compared to CORBA technology. DCOM is however tightly bound to the Windows operating system (Win32 API). Windows Runtime is a newer Microsoft technology that borrows much of the concepts of COM/DCOM.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    574 views20 pages

    Com, Dcom, Com+

    Uploaded by

    Peter R. Egli
    Overview of Microsoft COM / DCOM technology. DCOM is Microsoft's component technology and can be roughly compared to CORBA technology. DCOM is however tightly bound to the Windows operating system (Win32 API). Windows Runtime is a newer Microsoft technology that borrows much of the concepts of COM/DCOM.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 20

    COM DCOM - COM+

    indigoo.com

    COM, DCOM,
    COM+
    OVERVIEW OF MICROSOFTS COM, DCOM AND
    COM+ COMPONENT TECHNOLOGIES

    Peter R. Egli 2015

    Peter R. Egli
    INDIGOO.COM
    1/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    Contents
    1.
    2.
    3.
    4.
    5.
    6.
    7.
    8.
    9.
    10.
    11.
    12.
    13.

    Evolution of COM
    COM, DCOM, ActiveX, OLE, COM+
    Structure of COM Components
    (D)COM IUnknown Interface
    Component Lookup and Access
    Microsoft IDL File
    Execution / Access Models
    DCOM Architecture
    COM/DCOM/COM+ Tools
    Access (D)COM Objects from .Net (COM-.Net Interop)
    COM+ Applications
    Creation of COM Projects in Visual Studio
    Limitations of COM

    Peter R. Egli 2015

    2/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    1. Evolution of COM
    Over time Microsoft enhanced and rebranded the
    different object and integration technologies.
    .Net is a technological break because it
    is an entirely new technology.

    Object Linking and Embedding.


    Based on DDE.
    Technology for embedding and
    linking of documents in other
    documents.

    Fusing of COM/DCOM and


    MTS plus additional
    services.
    Uses COM as object
    technology.

    Renamed part of OLE


    related to networking.
    The parts of OLE relating
    to compound documents
    remained OLE.

    Distributed COM (COM over


    RPC).
    Technology with
    remotable objects.
    Microsofts answer to
    CORBA.

    COM+

    Component Object Model.


    Object technology
    confined to single machines.

    MTS

    ActiveX

    Dynamic Data Exchange.


    One of the first inter-process
    communication means in Windows
    Technology for compound
    documents (e.g. Word document
    with embedded Excel
    document).

    Microsoft Transaction
    Server.
    Runs on top of
    COM/DCOM, but is not really
    integrated with these
    technologies.
    Introduced transaction
    management, component
    deployment and other
    services.

    DCOM
    COM
    OLE

    DDE

    1987

    Peter R. Egli 2015

    1990

    1993

    1995

    1996

    1998

    2000
    3/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    2. What are COM, DCOM, ActiveX, OLE, COM+ ?


    COM is Microsofts object / component technology.
    DCOM = remote access to COM objects / components (wire protocol = MSRPC which is a
    version of DCE RPC).

    ActiveX/OLE uses COM as the underpinning. ActiveX / OLE provide additional services like
    reusable / programmable controls (OCX OLE Control Extensions), automation access
    between office documents and in-process activation.
    COM+ is the successor to the MTS/COM combo and provides a unified distributed
    component/object technology including the transaction services of MTS.
    COM+ uses the COM component specification and adds additional component services.
    Server

    Client
    MTS

    MTS

    ActiveX / OLE

    ActiveX / OLE

    DCOM
    COM+

    Peter R. Egli 2015

    COM

    COM

    MS RPC

    MS RPC

    COM+

    4/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    3. Structure of COM Components


    Relationship of objects, components, interfaces, classes, applications:
    A COM component contains 1..* objects.
    A COM component exists either as DLL (linked to the calling client, in-process) or as a
    separately running executable (out-of-process server).
    A COM object implements 1..* interfaces which are defined in the IDL-file.
    All objects (classes) of a component make up a type library.
    Every object has an IUnknown interface (see below).
    Component type library, every interface and every class / object has a globally unique ID
    (GUID, uuid).
    Component (DLL or exe)

    Notation:

    IUnknown
    uuid: 8DA10...124BC

    IViewer
    uuid: A42B8...791BA

    COM Object
    (CoViewer)

    IDAO
    IPersist

    COM Object
    (CoDAO)

    COM Object

    Client
    uuid: 71AA0...25A4C

    IUnknown
    uuid: 09B4C... 4A746

    Reference

    Type
    library

    Lollipop = (provided) interface.


    Arrow = call of a method of on the
    interface

    uuid: FD4AD...4255B

    uuid: 26B4D... D3C86

    Peter R. Egli 2015

    5/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    4. (D)COM IUnknown Interface


    Every COM object has an IUnknown interface.
    The IUnknown interface is used for:
    a. Introspection / reflection:
    Method QueryInterface() allows to dynamically discover other interfaces of an object (check
    if an object supports a specific interface identified by an interface ID).
    b. Life-cycle control / garbage collection (GC):
    AddRef() Client increases reference count.
    Release() Client releases its reference thus decrementing the reference count.
    GC collects object once the reference count becomes 0.

    IUnknown
    IViewer

    Component
    (DLL or exe)

    QueryInterface()
    AddRef()
    Release()

    COM Object
    (CoViewer)

    IDAO

    IUnknown
    COM Object
    (CoDAO)

    IPersist

    Peter R. Egli 2015

    6/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    5. Component Lookup and Access (1/3)


    Objects are registered in the registry under HKEY_CLASSES_ROOT/CLSID.
    Every object and interface has a registry entry.
    The registry is consulted for locating (lookup) objects based on a ProgID (mapping of
    GUID/uuid to implementation).
    Location of server DLL containing the object class

    Server type, here an inproc object (object is loaded into the clients process).
    Alternative: LocalServer32 object running in an executable.

    ProgID without version


    COMHelloWorld.COMHelloWorld

    ProgID containing the version


    Example COMHelloWorld.COMHelloWorld.1

    Peter R. Egli 2015

    7/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    5. Component Lookup and Access (2/3)


    Clients contact the SCM (Service Control Manager) in order to obtain an object reference.
    In case of remote objects (DCOM), the local SCM contacts the remote SCM.

    Server
    Component
    Client
    application

    1. Request with CLSID


    (GUID, uuid)

    5. Call on COM
    object

    Ixyz

    COM Object

    4. SCM passes
    reference to
    client

    SCM
    2. Lookup
    in registry

    3. SCM instantiates
    COM object

    Registry

    Peter R. Egli 2015

    8/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    5. Component Lookup and Access (3/3)


    Problem of registry-based component lookup:
    DLL-hell (different applications requiring different and possibly incompatible versions of
    COM-libraries).
    Solution:
    Registry free creation of objects (requires Windows XP or higher). Also called isolated COM.
    Different applications may use different versions of COM-components.
    COM-components no longer need to be registered but may be deployed with XCOPYdeployment (simple copying of components without creating registry entries by an installer).
    Component is described in a manifest file which is used by the calling application to load
    and create the component.
    Visual Studio settings (create manifest file as part of build):

    Source: http://msdn.microsoft.com/de-ch/magazine/cc188708(en-us).aspx

    Peter R. Egli 2015

    9/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    6. Microsoft IDL File


    IDL-files for COM use the MIDL-format (Microsoft IDL).
    IDL files are compiled with MIDL.exe (automatically in Visual Studio ATL-project).
    ...
    [

    COMHelloWorld.idl
    object,
    uuid(FD4ADCD2-C7FC-466E-AD75-EBC03024255B),
    dual,
    nonextensible,
    helpstring("ICOMHelloWorld Interface"),
    pointer_default(unique)

    ]
    interface ICOMHelloWorld : IDispatch{
    [id(1), helpstring("method ShowMessage")] HRESULT ShowMessage(void);
    [id(2), helpstring("method ShowMessageWithParam")] HRESULT ShowMessageWithParam([in] BSTR message);
    };
    ...

    MIDL.exe

    HelloWorld.h

    ...
    public:
    STDMETHOD(ShowMessage)(void);
    public:

    STDMETHOD(ShowMessageWithParam)(BSTR message);
    };
    ...

    Peter R. Egli 2015

    HelloWorld.cpp

    COMHelloWorld.h

    COMHelloWorld.cpp
    10/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    7. Execution / Access Models


    In-proc access:
    Local server:
    Remote server:

    Client machine

    Component resides in a DLL.


    The client loads the component into its process.
    Component resides in an executable and runs in its own process on the
    local machine. Access through RPC.
    Component resides in an executable and runs on a remote machine.
    Access through RPC.
    In-process
    access

    COM
    COM Object

    Stub

    Local
    server

    Client
    RPC
    Local proxy

    Remote
    server

    COM Object
    COM

    Remote machine

    Remote
    proxy
    Client process

    COM
    Stub
    RPC

    Peter R. Egli 2015

    COM Object

    11/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    8. DCOM Architecture
    Client proxy:
    Stub:
    Registry:
    SCM:

    Proxy object on client side for accessing the server object.


    Server interface stub that complements the client interface proxy.
    Contains a list of mappings of class / object GUID to implementation library.
    Service Control Manager (RPCSS.exe) which consults registry and creates /
    instantiates a new server object based on the GUID (comparable to ORB in CORBA).
    The SCM hides the registry from (D)COM.

    Client
    COM Object

    Server

    Client
    component
    library

    Interface on SCM for


    remote activation:
    IRemoteActivation::
    RemoteActivation

    Interface
    proxy

    COM Object

    Interface
    stub

    SCM

    SCM

    RPC

    RPC
    Actual access to
    remote object is done
    through RPC

    Peter R. Egli 2015

    Server
    component

    Registry

    ORB: Object Request Broker


    12/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    9. COM / DCOM / COM+ Tools


    Register COM component:
    regsvr32 <COM-lib>.dll
    Registry of objects:
    Windows registry (edit with regedit.exe or regedt32.exe)
    Component service explorer:
    Control Panel Administrative Tools
    Component Services
    or simply start dcomcnfg.exe

    Peter R. Egli 2015

    13/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    10. Access (D)COM Objects from .Net (COM-.Net Interop)


    .Net introduced an entirely new object model:

    .Net object lifetime is managed by garbage collector (COM: lifecycle controlled by client).
    .Net clients have far greater introspection possibilities through reflection.
    .Net objects reside in a managed environment (managed code).

    The .Net environment (CLR: Common Language Runtime) provides wrappers for COM-.Net interoperability:
    COM.Net:
    COM callable wrapper CCW .
    .NetCOM:
    Runtime Callable Wrapper (RCW).
    The wrappers are contained in DLLs called Interop.xxx.
    Tasks of wrappers:
    Marshalling of parameters (e.g. MFC-type BSTR .Net string)
    RCW: COM object reference counting (RCW); decreases reference count on COM object if object is no
    longer needed on .Net managed side.
    .Net object reference release (CCW); map COM-side Release() call to .Net managed object release
    COM

    .Net

    Source: http://msdn.microsoft.com/en-us/library/5dxz80y2.aspx
    Peter R. Egli 2015

    14/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    11. COM+ Applications


    COM+ applications host (contain) 1..n COM-components.
    Dcomcnfg.exe shows a list of active COM+ applications.

    COM components
    of COM+ Utilities COM+
    application

    Peter R. Egli 2015

    15/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    12. Creation of COM Projects in Visual Studio (1/4)


    1. Create Visual Studio ATL C++ project with the following settings:

    2. Add a new class to the COM component:

    Peter R. Egli 2015

    16/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    12. Creation of COM Projects in Visual Studio (2/4)


    3. ATL Simple Object Wizard:
    Set names (Class, Coclass and Interface names may be different):

    4. Add method to interface (e.g. ShowMessage()):

    Peter R. Egli 2015

    17/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    12. Creation of COM Projects in Visual Studio (3/4)


    5. Implement interface method (ShowMessage()):
    Add user code to implementation of method in implementation class (HelloWorld.cpp):
    STDMETHODIMP CHelloWorld::ShowMessage(void)
    {
    ::MessageBox(::GetActiveWindow( ),_T("Hello World from COMHelloWorld."),
    _T("First COM+ Application"),MB_OK);
    return S_OK;
    }

    6. Compile ATL COM project


    7. Register COM:
    Open command shell, change to debug directory of COM project.
    >regsvr32.exe COMHelloWorld.dll
    8. Create client, e.g. in Excel-VBA:
    Create new Excel file
    ToolsMacroVisual Basic Editor
    Add reference to COM component (ToolsReferences):

    Peter R. Egli 2015

    18/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    12. Creation of COM Projects in Visual Studio (4/4)


    9. Access the COM component from VBA code:
    'TestHelloClient_TLB accesses the COM component using the COM type library (TLB)
    'that has to be added to this project in the references (Menu Tools->References)
    Sub TestHelloWorldClient_TLB()
    Dim hw As COMHelloWorld
    Dim gw As COMGoodbyeWorld
    Set hw = New COMHelloWorld
    hw.ShowMessage
    Set gw = New COMGoodbyeWorld
    gw.ShowMessage
    End Sub
    'TestHelloWorldClient_ProgID access the COM component using the ProgID
    Sub TestHelloWorldClient_ProgID()
    Dim obj As Object
    Set obj = CreateObject("COMHelloWorld.COMHelloWorld")
    obj.ShowMessage
    Set obj = CreateObject("COMHelloWorld.COMGoodbyeWorld")
    obj.ShowMessage
    End Sub
    ATL project name

    Coclass name

    Object ProgID
    Peter R. Egli 2015

    19/20
    Rev. 1.60

    COM DCOM - COM+

    indigoo.com

    13. Limitations of COM


    COM is still widely used by many applications to provide programmatic access for automation
    purposes.
    However, due to many technological limitations (see below) COM was technologically
    superseded by .Net.
    No true inheritance (may be emulated with aggregation and containment).
    No exceptions (only return codes).
    Inconsistent use of IDL (COM uses IDL, but VB or scripting languages like VBA use binary
    representation (type library)).
    No OO-features (static modifier, virtual functions, overloaded methods).

    Peter R. Egli 2015

    20/20
    Rev. 1.60

    You might also like