Home/ Questions/Q 7982191
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T10:36:21+00:00

How can I read out all property names via reflection of an COM Object

  • 0

How can I read out all property names via reflection of an COM Object in C#?
I know how to get the property if I know the name.

comObject.GetType().InvokeMember("PropertyName", System.Reflection.BindingFlags.GetProperty, null, comObject, null);

but what is when I want to dump all properties?

PropertyInfo[] properties = t.GetProperties();

This way didn’t work with Com-Objects. If I do a GetMembers() I get these Members:

Name: GetLifetimeService
Name: InitializeLifetimeService
Name: CreateObjRef
Name: ToString
Name: Equals
Name: GetHashCode
Name: GetType

regards Chris

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You got the members of the __ComObject class, the underlying .NET class for an RCW.

    COM has a wee bit support for reflection, as long as the COM coclass implements IDispatch, the Automation interface. Not unusual, it is the interface that scripting languages use to make calls. IDispatch.GetIDsOfNames() is always implemented, but you have to know the name of the member up front. IDispatch.GetTypeInfo() gives access to the type library for the coclass, but isn’t always implemented. Translation of type library info to metadata is an imperfect art, the core reason why .NET wants you to do this upfront with Tlbimp.exe. If you want to pursue a runtime approach then you’ll probably benefit from the source for the managed version of Tlbimp, available here.

    Doing this up front at build time is always best, you do so by adding a reference to the type library (usually embedded in the executable file) or by running Tlbimp.exe yourself. Now you got a .NET interop wrapper class that has all of the members of the underlying COM coclass and interfaces. At which point you probably don’t need reflection anymore 🙂

    • 0