T
Tim Rogers
For some unknown reason, when I compile my MC++ app now, I get this error
during the
link phase. Apparently VS .NET needs ole32.dll to link
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
that we've changed our project directory structure somewhat. My project is
a managed wrapper for an unmanaged C++ API.
Here is the information I know thus far:
1) This error only occurs during DEBUG builds.
2) Currently, my project links to static libraries (some our code, some 3rd
party - ACE & open SSL in particular). If I change the project to use the
DLL equivalents, then the error goes away.
Any ideas out there?
Thanks,
Tim Rogers
during the
link phase. Apparently VS .NET needs ole32.dll to link
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
that we've changed our project directory structure somewhat. My project is
a managed wrapper for an unmanaged C++ API.
Here is the information I know thus far:
1) This error only occurs during DEBUG builds.
2) Currently, my project links to static libraries (some our code, some 3rd
party - ACE & open SSL in particular). If I change the project to use the
DLL equivalents, then the error goes away.
Any ideas out there?
Thanks,
Tim Rogers