I have a COM object (implemented in C++) that works fine from VBA (in Excel)
and other environments, but doesn't work from within .NET when called by a
C# application. The function typecasts the IDispatch* to the C++ type it
knows it must be and accesses some private members.
1. How can I debug this function? If I set a breakpoint, it gets ignored
and a ? put in the margin instead of a circle. If I use DebugBreak() it
doesn't do anything.
2. Does .NET do anything funny with its 'object' type like return a proxy
rather than the original object? I am calling the COM object method within
an event handler for an event from that object, and I pass the 'object'
received in the event handler directly to the method.
Thanks,
Aaron Queenan.
Aaron Queenan - 31 Jul 2003 17:49 GMT
I have a COM object (implemented in C++) that works fine from VBA (in Excel)
and other environments, but doesn't work from within .NET when called by a
C# application. The function typecasts the IDispatch* to the C++ type it
knows it must be and accesses some private members.
1. How can I debug this function? If I set a breakpoint, it gets ignored
and a ? put in the margin instead of a circle. If I use DebugBreak() it
doesn't do anything.
2. Does .NET do anything funny with its 'object' type like return a proxy
rather than the original object? I am calling the COM object method within
an event handler for an event from that object, and I pass the 'object'
received in the event handler directly to the method.
Thanks,
Aaron Queenan.