This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: QueryInterface Failure Probe in CLRSpy
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
The Man has described a very useful probe that you will need for certain COM Interop problems with RCWs and its underlying QI call. The QI failure it detects is when a QueryInterface call fails in the object's original context, but the CLR has determined that this COM object is a standard proxy (because the interface pointer's address is in the range of the loaded ole32.dll). CLRSpy is a must-have tool for COM Interop but you already know that right?
Previous Topic
