Replies: 2 comments
-
The answer, I believe, is in the first graphic: "To inspect the native object, enable native code debugging." The objects exposed by Vanara are native COM objects, with no Runtime Callable Wrappers. The objects exposed when adding a COM reference are RCWs and have special handling within .NET. See here for instructions. |
Beta Was this translation helpful? Give feedback.
-
Hello and happy new year! I've tried your suggestions and I get the following debugging experience: So it shows something but none of the actual properties, I suppose it's expected as these are methods on native side. As I understand you, it's these RCWs that make the properties available during debugging, correct ? Which leads me to ask you, could a custom build of Vanara leverage these RCWs ? or anything else Thank you. |
Beta Was this translation helpful? Give feedback.
-
Using the IMAPI package, when you debug the program, you can't see any of the properties for a COM object in the debugger:
On the other hand, when you manually add a COM reference using the Visual Studio wizard, during debugging you can see the properties of COM objects:
But then of course, when going this way one loses all of the fantastic plumbing and helpers provided by Vanara...
Any ideas on how to have the best of both worlds, i.e. get Vanara to show properties of COM objects in debugger?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions