> 1) List the complete set of interfaces our server supports - or must I go > through all ones I expect it to support and try QueryInterface on them all > and see which work? I can do that at a stretch (I think I can get the list > of what such a server should support at full implementation), but if there > was something like DumpBin to list the supported interfaces instead of DLL > exports, that would be sooooo helpful. I'm happy to write a few lines of > code to get that concise list if necessary.
There is: oleview.exe. > 2) Is there any way to snoop on what interfaces are being requested, like > Spy snoops on Windows messages being sent to a window? That could tell us > what is being requested and we could try it ourselves to see which work. In > fact the snoop might even be able to tell us right there whether it > succeeded or not. In ATL, there is. It's a preprocessor flag you need to define before all headers. I don't remember it exactly, but off the top of my head it's something like _ATL_DEBUG_QI (probably not, though!). Check out the ATL predefined macros in the MSDN, and it lists the macro there. Too lazy to do it myself as you see! :-) -- Ehsan Akhgari Farda Technology <http://www.farda-tech.com/> The difference between genius and stupidity is that genius has its limits. -- Albert Einstein _______________________________________________ msvc mailing list msvc@beginthread.com See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
