Hi,
I've a migration scenario where I rewrite a COM object to an .NET interop
assembly (so, still callable from COM). What is the impact if I continue my
step-by-step migration and have a scenario where my .NET objects start to
call .NET interop assemblies? Is there an overhead included?
For example, I've three objects: A (fully COM), B (interop assembly) and C
(.NET assembly).
A calls B and C calls B. From A to B is done through the CCW. Is C to B than
done through the RCW since my interop assembly still has a COM interface?
Is there a difference in B and C anyway, is there a wrapper involved?
Should a think of custom-managed wrappers in case of the C to B call?
Any input is very much appreciated (couldn't find the details in the MSDN
docs).
Regards,
Onno Ceelen
Phil Wilson - 21 Nov 2003 18:58 GMT
I think I've heard that the calling sequence .NET COM client =>RCW=>CCW=>.NET
COM Server isn't supported. A COM-callable wrapper is intended for use by COM
clients, not runtime-callable wrappers.

Signature
Phil Wilson [MVP Windows Installer]
----
> Hi,
>
[quoted text clipped - 19 lines]
>
> Onno Ceelen