Author Topic: Windows binary fails due to lack of msvcr70.dll  (Read 792 times)

James Gregory

  • Wayfarer
  • *
  • Posts: 4
    • View Profile
Windows binary fails due to lack of msvcr70.dll
« on: December 25, 2004, 03:25:51 am »
On the \"Known bugs\" page you say there is a known bug
with MSVCP70.DLL. Note VCR/VCP difference. Is this a
typo, or are other people having an issue with a
different dll as well?

Also, I think you should suggest people put these dlls
in their planeshift directory, not the win32 directory.
This is what Microsoft say you should do at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;326922

\" When you build an application in Visual Studio .NET
that uses the C run-time libraries (CRT), distribute
Msvcr71.dll/Msvcr70.dll with your application and
install the DLL in your Program Files directory. Do
this instead of installing the DLL in the system
directories. Do not assume that the DLL already exists
in the system directories.

Note Microsoft Visual C++ .NET 2003 (.NET Framework
1.1) uses Msvcr71.dll as the CRT DLL. However,
Microsoft Visual C++ .NET 2002 (.NET Framework 1.0)
uses Msvcr70.dll as the CRT DLL.
MORE INFORMATION
The shared C Runtime (CRT) DLL has been distributed by
Microsoft in the past as a shared system component.
This may cause problems when you run applications that
are linked to a different version of the CRT on
computers that do not have the correct versions of the
CRT DLL installed. This is commonly referred to as the
\"DLL Conflict\" problem.

To address this issue, the Msvcr71.dll/Msvcr70.dll is
no longer considered a system file, therefore,
distribute Msvcr71.dll/Msvcr70.dll with any application
that relies on it. Because it is no longer a system
component, install it in your applications Program
Files directory with other application-specific code.
This prevents your application from using other
versions of the CRT library that may be installed on
the system paths.\"