For some reason, when I compile my MC++ app now I get this error during the
link phase. The file DOES exist and is in the proper place in the path.
The only difference between when I could link successfully and now that I
can't is an upgrade in a 3rd party static library (ACE) that my project is
linking to. (My project is a managed wrapper for an unmanaged C++ API.)
I assume this new library could be causing the problem, but I have NO idea
why.
Any ideas out there?
Thanks,
Tim Rogers
George Ter-Saakov - 09 Sep 2003 18:25 GMT
You do not link to ole32.dll.
You link to ole32.lib
George.
> For some reason, when I compile my MC++ app now I get this error during the
> link phase. The file DOES exist and is in the proper place in the path.
[quoted text clipped - 10 lines]
>
> Tim Rogers