Comments on: Getting IUnknown from __ComObject

By: Beware of using stack-based COM objects from .NET

Beware of using stack-based COM objects from .NET — Thu, 21 Jan 2010 17:17:00 +0000

[...] If we run the app again, and this time break while it’s waiting for the keypress, before it attempts to clean up the RCWs, then we can examine the wrapper ourselves, using the approach I set out in this post. [...]

By: ian

ian — Tue, 03 Nov 2009 17:07:37 +0000

I put together an initial version, but I’m not sure it’s ready for the world! I’ll take another look and try and upload something very soon.

By: Thomas

Thomas — Mon, 02 Nov 2009 19:41:49 +0000

Hey, that’s absolutely interesting. Did you find the time to write the WinDbg extension for this? I have lots of COM-Interop and would appreciate a little help analyzing some exceptions. Thanks!

By: A .NET Application that Never Dies | Bob on Medical Device Software

A .NET Application that Never Dies | Bob on Medical Device Software — Sat, 19 Sep 2009 23:10:57 +0000

[...] I ran across a post about COM object memory allocation in mixed managed/unmanaged environments: Getting IUnknown from __ComObject. As this article exemplifies, debugging COM objects under these circumstances is a real pain in the [...]