In this case don't forget to add the appropriate 'policy merge module' to avoid errors caused by incorrect runtime version.įinally, you can just put required DLLs in the same folder in which your application is installed. It may be done by specifying this requirement in prerequisites property in your setup project.Īlso, you can distribute the runtime dll by including in your setup project the appropriate ' merge module'. Using /MD is highly recommended to avoid such lossage.Īnother possible solution is to require an appropriate Microsoft Visual C++ Redistributable package to be installed on the user's machine.

Problems when you have more than one 'errno' variable for example.

Problem with earlier versions of VS where each CRT would get its own With multiple copies of the CRT in your program. Using /MT is risky if you create DLLs as well as an EXE.

To be more specific, I'll allow myself to quote a part of this answer: Possible solution is to link statically with runtime library, but it may cause a lot of problems in case you have both. This is because their compilers link against msvcrt80.dll, msvcrt90.dll, msvcrt100.dll, msvcrt110.dll, msvcrt120.dll and msvcrt140.dll respectively, which are not shipped with Windows. However, if you are developing in VS 2005, VS 2008, VS 2010, VS 2012, VS 2013 or VS 2015, you have to distribute additional C runtime libraries along with your application. Visual Studio 6.0's compiler links against this library, so if you are developing in VS 6.0 you shouldn't encounter any problems on most users' machines. These include string manipulation, memory allocation, C-style input/output calls, etc. This library provides a typical set of library functions required by C and C++ programs. The only version of the C runtime library which is shipped by Microsoft with most of 32 bit Windows versions is msvcrt.dll.

Visual studio redistributable