Manifest issues with VC2005

Hot Topic

Command Line Arguments
How can I manipulate strings in ATL
Function decorated names in DLL lib
C++ .NET Managed Code - Excel 2000
Windows services in VC Express
Char To String (help me)
VCMAME: compiles with VC2003, fails with VC2005
Compiling VS 2005 Beta2 to a mounted network share
GDI Logical Mapping Modes in MFC
Visual C++ 2003 Standard -> how to upgrade

Visual C++

Dynamic add controls to a dialog frame.
fatal error LNK1104: cannot open file 'LIBC.lib'
Viewing GIF Frames separately
__box
Form Closes without this->close() being called
LNK problems continued
where can I include the object/libray modules(opengl32.lib glu32.lib glaux.lib ) in vc++.net?
binaries compiled using VC8 not running on IA64
Problem Converting char** to cli::array<System::String^>^ and vice-versa
graph.h

Manifest issues with VC2005

Hi I'm trying to build a production application in debug using Visual Studio 2005. The application builds, but when I go to run it in debug, I get an error that it can't find the Release versions of the run-time libraries. I've looked at a lot of documentation and discussion groups regarding manifests and have not found out what to do. It looks like the manifest (as near as I can tell) has the debug versions of the libraries included, but not the release versions. My application is a mix of OEM libraries and ours, some of which are release builds. How can I get this to work Is there some wat to add the release versions to the manifest

Answer this question

Manifest issues with VC2005

  • ddodson

    As additional reading for manifests and redistributables, see this FAQ.

  • FleetCommand

    Could you post the manifest in question

    Thanks,
      Ayman Shoukry
      VC++ Team

  • Alene

    I see some problems with your scenario

    1. Mixing Debug and Retail CRT in the same binary can cause problems. You should try to get versions of the OEM Libraries that link to Debug CRT.

    2. Using Debug CRT in production environment is not recommended. Redistributing Debug VC libs DLL is not allowed. Please see the EULA for details.

    What does dumpbin /imports  on your binary report Does it list msvcr80.dll and/or msvcr80d.dll

    Thanks,
    Sridhar Madhugiri
    Software Developer
    Visual C++



  • pomp

    Sometimes you just don't get third party libs build against a debug CRT! What can you do then In former versions of MSVC, it was possible to mix it to be at least able to debug a part of your program. Further more it is sometimes where expensive in a runtime point of view, to use all libraries as debug libraries.
    So why has the behaviour of MSVC 8.0 changed (compared to version 6.0, 7.x) concerning the mixture of debug/non-debug CRT

    Regards,

    Wolfgang

  • JorgeCM

    I don't see how the FAQ concerning manifests and redistributables explains anything to solve the problem of mixing debug and release versions of libraries/executables in case where I simply need to debug an application but don't have access to debug versions (i.e. versions linked against the debug CRT) of third party libraries.

    Regards,

    Wolfgang
  • Manifest issues with VC2005
Answer this question