Hi > 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.
If I understant your problem correctly, you should be able to set the 3rd part DLL up as a reference in something like VB and then use the reference viewer to list the interfaces and associated fucntions. Out of interest what is the point of your COM server? Is it simply to provide an instance for the 3rd party DLL? > 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. I haven't actually done any COM for a very long time (I miss it really), but I assume you're using ATL and you should be able to find in the code where query interface goes through the supported interfaces, but I could be wrong. Regards Paul Paul Grenyer email: [EMAIL PROTECTED] web: http://www.paulgrenyer.co.uk Aeryn: http://www.aeryn.co.uk Heaven can wait. _______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
