VS 2005 creating manifest with 2 entries for the VC runtimes?

  • Thread starter Thread starter Satish
  • Start date Start date
S

Satish

My vc++ app is building without errors but will not run. Here's the manifest
generated below. I think this is due to me having 2003 and 2005 installed
from what i have researched on the web. Any ideas on stopping this from
happening?


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50608.0" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
<dependency>
<dependentAssembly>
<assemblyIdentity type="win32" name="Microsoft.VC80.DebugCRT"
version="8.0.50727.762" processorArchitecture="x86"
publicKeyToken="1fc8b3b9a1e18e3b"></assemblyIdentity>
</dependentAssembly>
</dependency>
</assembly>
 
My vc++ app is building without errors but will not run. Here's the manifest
generated below. I think this is due to me having 2003 and 2005 installed
from what i have researched on the web. Any ideas on stopping this from
happening?
Click to expand...

I don't think it's due to having 2003. I suspect it's due to using
libraries built with a subtly different version of VS2005 - a possible
pre/post SP build issue.

Dave
 
Thanks for the tip David.

My collegue is building his libs with SP.050727-6700 and I'm using
RTM.050727-4200. Is there no clean workaround other than standardizing to
the same version of VS?
 
My collegue is building his libs with SP.050727-6700 and I'm using
RTM.050727-4200. Is there no clean workaround other than standardizing to
the same version of VS?
Click to expand...

None that would be "clean".

Dave
 
Back
Top