In-proc server is a COM component, when instance is the
server is loaded into the caller process space. In-Proc
server can be easily identified by .dll extension.
Out-of-Proc server is a COM component that run in its own
process space and for any instances created by the users, a
proxy is created within the users process space. Proxy is
responsible for interacting with the server to carry out
operation on behalf of the client. (.exe extension).
For the first question, Yes, we can since the QueryInterface
() rules of thumb suggest that if we can query an interface
of C from B, we should be able to query the viceversa.
The IUnknown implementation of both the objects has to do
For the second question, Aggregation bounds outer and inner
objects together and gives the user the interface pointers
of either objects to access it directly so that the user
never knows the objects are aggregated.
But when containment is used, the interface of inner object
never exposed to the client directly rather the outer
object receives the calls and forwards internally. Here
also, the user doesn't know the objects are contained.
An object that implements the IMoniker interface. A moniker
acts as a name that uniquely identifies a COM object. In
the same way that a path identifies a file in the file
system, a moniker identifies a COM object in the directory
OLE is a set of technologies to support linking and
embedding. COM lies in OLE as one of the technologies. COM
defines a binary standard / set of rules for developing
To create the instance of COM componet use the following
To access the component that was there in local system use
To access the COM componet remotely use the following API
- Reads RootClassesProgId for the matching ProgID
- Reads RootClassesProgId for the matching CLSID. The
CLSID is read from the above step.
- From the CLSID key, the server type and image filename is
- Depending upon the server type, it starts the server.
- Calls CoGetClassObject function to get a handle to the
- Then calls createinstance on the factory interface to get
the pointer to the derived object.
eturns a pointer to the current interface if successful or
IUnknown is a type of COM Interface.
Every COM class implements an interface named IUnKnown.
IUnKnown contains three methods:
1) HRESULT QueryInterface()
2) ULONG AddRef()
3) ULONG Release()
Query Interface method is used to get the pointer to the
interface specified in one of the parameters of this
method. Client then uses this pointer to call the method of
AddRef and Release are used to increase and decrease the
count of the instance of component loaded in memory
respectively. when the count reaches zero the component is
Open the dll in dependency walker application
(depends.exe). If the dll is having following functions
It is a COM DLL otherwise it is not.
1. Defines a binary standard for component interoperability
2. Is programming language-independent
3. Is provided on multiple platforms (Microsoft® Windows®,
4. Microsoft Windows NT™, Apple® Macintosh®, UNIX®)
5. Provides for robust evolution of component-based
applications and systems
6. Is extensible
CoInitialize will initialize the COM library and will move
the executing thread to a STA or Single Threaded Apartment
Apartment is the logical entity where threads live.
COM Dll exposes Interface on the contrary to normal DLL
that exports functions. Clients create the pointer to
COMDLL's interface to call the methods defined by the
component that implements the interface.
That results in isolation of implementation and definition
of method in the interface. Client doesnt need to relink or
recompile the code if method in the com dll changes as far
as the definition of the interface remains same.
COM (Component Object Model) technology in the Microsoft
Windows-family of Operating Systems enables software
components to communicate. COM is used by developers to
create re-usable software components, link components
together to build applications, and take advantage of
Inorder to call your DLL as COM dll, you have to follow
some rules to develop the dll. If those rules are there
then only your DLL will be called as COM dll.
COM is a specification set of rules to develope binaries,
COM is not a language.
Object references in COM is accounted using two methods of
IUnknown Interface (AddRef and Release).
AddRef: Increments a reference count whereas "Release"
decrements the count.
When the count of the reference is zero the DLL is unloaded
Structs, also known as User Defined Types (UDTs), can be
used in Automation- compatible interfaces
An Automation- compatible struct may contain only primitive
Automation types as its members.
Nesting structs is not allowed, but VARIANT is allowed thus
enabling nested structs (you can store a struct in a
In order for a struct to be usable for Automation-
compatible interfaces, the struct must be described in a
type library and it must be declared with its own GUID:
[helpstring("A long value")]
// Later in the IDL file
[uuid(...), version(...), helpstring(...)]
There are two kind components
We can use both as DCOM servers, its upto our design.
While accessing the DCOM component you have to provide
COSERVERINFO structure. This structure is having the
information about where the component is.
QueryInterface to A will delegate request to B which, in
turn, will delegate request for the interface to C. This
pointer will be returned to the client.
Queued Components, a key feature of COM+ and based on
Microsoft Message Queuing Services (MSMQ), provides an easy
way to invoke and execute components asynchronously.
Processing can occur without regard to the availability or
accessibility of either the sender or receiver. A home
shopping network is an example of the type of application
that might benefit from asynchronous processing. In this
asynchronous, disconnected scenario where viewers phone in
to several operators, orders are taken en masse and are
then queued for later retrieval and processing by the
RCW is used for making a NET compnent talk to a com component.
CCW is used for Com to .NET communication