• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Exposing COM Interface

implemnt i dispatch or go the i uknown/iqueryinterface way

you probably should get a book on com if you dont know what i am talking about.
 
I know that if you started the project as an ATL project, then you could simply Create a new ATL object, and it'll auto-generate all of these IUNKNOWN/IDISPATCH stuff, however, the EXE wasn't created as an ATL project. Is there a way for me to still get vc++ 6.0 to autogenerate the stuff for me?
 
Is there a way for me to still get vc++ 6.0 to autogenerate the stuff for me?

In short: no.

You can't simply take a PE executable and have it automatically generate a COM component out of it. There are many reasons why this is so... a few are noted:

1) Your executable probably doesn't export (__declspec(dllexport) or in your .def file) any functions, so it couldn't simply permute the routines in your program and generate the IDL necessary for COM, etc.

2) Even if the above were possible, you're probably not returning HRESULTs.

Do you have the source code to this other project?
 
Back
Top