Home/ Questions/Q 6217775
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T07:29:03+00:00

Is it possible to force a COM Visible .NET assembly to instantiate as System.__ComObject,

  • 0

Is it possible to force a COM Visible .NET assembly to instantiate as System.__ComObject, rather than it’s .NET type? The reason I ask is, part of my app uses 3rd party COM objects, but some of those, when written in .NET, get instantiated as their .NET types and break the object handlers I’ve created. I have no control over methods used to create the COM objects. Currently I’m using the following to create the objects.

Type comType = Type.GetTypeFromCLSID(objectGUID);
comObject = Activator.CreateInstance(comType);

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Actually, no.

    The COM activation of managed objects is done in the same AppDomain as the caller. IMHO, This is a nasty issue with COM interop in .NET. There are several questions here on SO with all sorts of attempts at making this work. I can attest that I’ve tried most of these to no avail. Your COM API provider SHOULD be producing a PIA (Primary Interop Assembly) to ensure forward type compatibility. If they are not, you are going to have some nasty issues.

    The only workaround I’m aware of as a client is to only use the ‘object’ type. Everything would need to go through reflection. Some things you still can’t do. For example, you would not be able to implement an interface.

    I havn’t a clue why this works this way. It’s caused me no end of problems producing a viable api for both unmanaged and managed code.

    • 0