In my last article, I briefly discussed how COM, Sxs and CLR
work together to make registration free COM/.Net interop
possible. Today, I want to dive a bit deeper into this feature.
Specifically, I want to discuss  1.       How activation works
end to end.  2.       How to generate manifests for managed
assemblies  3.       What are the constraints of registration
free COM interop.   In a typical Registration Free COM interop
scenario, there is a managed assembly as the COM server. The
managed assembly has a SxS manifest describing the COM
registration information. There is also an unmanaged COM client.
The client has a Sxs manifest with the managed COM server as its
dependency.    During the COM activation, the following
sequences happen in order:  1.       CreateProcess is called on
the COM client  2.       Inside CreateProcess, Sxs detects that
the COM client has a Sxs manifest.  3.       Sxs parses the
client’s manifest. For all the dependencies specified in the
client’s manifest, Sxs finds the manifests