There is also a LIBCMT.LIB which is used if C code is linked statically to the CRT environment. MSVCM*.DLL – This DLL contains C/C++ run-time routines used for mixed mode (managed and native) programming.When C/C++ code is linked dynamically to CRT, Visual Studio will link it against appropriate version of MSVCR*.DLL and MSVCP*.DLL. – such as standard template classes ( basic_string, vector, set, iostream, etc.), C++ implementation of math library, etc. MSVCP*.DLL – This DLL contains C++ run-time routines, classes and templates, etc.When C code is linked dynamically to CRT, Visual Studio will link it against appropriate version of MSVCR*.DLL.

MSVCR*.DLL – This DLL contains C run-time routines – such as printf, scanf, fgetc, ceil, getenv, putenv, isdigit, etc.Visual Studio C/C++ run time environment (CRT environment) consists of the following dynamic libraries: Visual Studio Runtime Environment Explained Mapping between Visual Studio product names and corresponding internal version numbers is as follows: Visual Studio C/C++ run time libraries contain Visual Studio internal version numbers. Template Classes, In-Line & Template Functions.Function Calls taking/Returning C/C++ Objects.In particular, we will explore this topic in following context: managed code), so I will limit this discussion to code developed in native C/C++ programming language only.

I have not explored this topic in detail for. We will also see what can be done to avoid potential issues if multiple Visual Studio versions can’t be avoided. Let’s explore in detail various issues surrounding the topic of using multiple Visual Studio versions in the program. I also see responses such as – “this should not be a problem” or “I do this all the time without any issues”. Very often, in various programming forums, I see questions about mixing multiple Visual Studio versions in the program. For example: a program using LibA.dll that is compiled against Visual Studio-2005 and LibB.dll that is compiled against Visual Studio-2008. I have seen countless number of hours being lost trying to get to the bottom of such failures, only to find out that the cause of the unexplained behavior was that the program used DLLs compiled against multiple Visual Studio versions. Everything seems fine, inputs are OK, memory allocations seem fine, code does not seem to contain any bugs yet it fails spectacularly. They scratch their head trying to debug their code. Either their program crashes randomly or it simply crashes for no apparent reason. Many times I have seen programmers complain that they see some strange behavior during testing something that they cannot explain.

Microsoft visual studio 2008 c compiler