Page 2 of 2
Posted: Fri Apr 06, 2007 4:45 pm
Unfortunately I'm not sure how the alternate method can be used in VStudio.
Posted: Fri Apr 06, 2007 6:45 pm
Ok I got it fixed but I don't understand the underlying cause.
I figured out that the root cause was that the manifest file that's being produced is incorrect.
After searching on my harddisk for MSVCR80D.DLL I found it in a hidden directory which is correct but the version number of this dll does not match the version number specified in the manifest! I have no idea why this is and where Visual Studio is getting this version number.