Creating COM by using ATL dll to wrap C++ MFC unmanaged dll

[Member 3480232]

I am in charge of a large number of dll's written in MFC. I have made a decision to convert them to COM interfaces. I studied the subject and decided ATL is the best answer. Problem is: I cannot call the old dll methods without getting a LNK2019 error. The IDE is VS2003. I read something about there being a issue with VS2003 with the 'attribute' keyword. A nudge in the right direction would be highly appreciated.

[Roger Stoltz]

Member 3480232 wrote:

I cannot call the old dll methods without getting a LNK2019 error.

Which means that you're doing implicit linking, i.e. you're not calling ::LoadLibrary() and ::GetProcAddress() to make use of your libraries. This also means that you need to link with the .lib file generated in the build process of the library you're trying to use. Now to the obvious question....: have you added the .lib file to the "additional libraries" in your project settings?

"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown

[Member 3480232]

Right on all counts. The original job was done by myself, so everything is as I hoped it should be. I also include the old job.h file with the cplusplus override added. Its obvious I am doing something wrong! As an afterthought, part of the decision to do this had to do with the schlepp of using LoadLibrary, GetProcAdress or DllImport and possibly speed of linking as well.