Re: RCW/CCW between COM and .NET

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Robert Jordan (robertj_at_gmx.net)
Date: 08/26/04 

Date: Thu, 26 Aug 2004 22:51:21 +0200

> Now, assuming that I have a .NET component that is COM creatable as
> described above. If I create this Com creatable .NET component from an
> external .NET component via the Activator methods (used
> Type.GetTypeFromProgID) am i talking to an RCW for my external .NET component
> that is talking to a CCW for the .NET com createable object? Or is .NET
> smart enough to realize that an RCW and a CCW are not required since both
> objects are .NET objects, even though I created it via a traditionally COM
> manner? Is there any way to really test this?

wow, that a good point! ;-)

however, it's quite easy to prove: test whether the object you get
from Activator is a System._ComObject. or use Marshal.IsComObject.

bye
rob

Relevant Pages

  • RCW/CCW between COM and .NET
    ... I understand that if I use Activator object to create a COM object from its ... I also realize that my .NET component is creatable via CoCreateInstance ... Type.GetTypeFromProgID) am i talking to an RCW for my external .NET component ... that is talking to a CCW for the .NET com createable object? ...
    (microsoft.public.dotnet.framework.interop)
  • networking in XPe
    ... Is the .NET component required to browse to an XPe computer. ... I've enabled sharing and the guest account. ... Rob ...
    (microsoft.public.windowsxp.embedded)