Revision as of 12:39, 28 April 2023 edit Efa (talk \| contribs) Extended confirmed users 1,307 edits added refs for C99 compliance ← Previous edit		Revision as of 22:58, 21 June 2023 edit undo Ayfaouzi (talk \| contribs) 2 edits m There is no such Version of Visual C++ that is 13.0. It was probably confused with Visual C++ 2013 but the MSVC version is 12.0. This Microsoft blog confirms this: https://devblogs.microsoft.com/cppblog/the-great-c-runtime-crt-refactoring/ Next edit →
Line 91: It has shipped with Windows versions since Windows 95 OSR2.5 for use by other Windows components; earlier versions shipped with the '''CRTDLL.DLL''' library instead. In older versions of Windows, programs which linked against MSVCRT.DLL were expected to install a compatible copy in the System32 folder, but this contributed to [[DLL Hell]] because many installers failed to check the library version against the installed version before replacing it. Versions of MSVC before 4.0 and from 7.0 to 1312.0 used differently named DLLs for each version (MSVCR20.DLL, MSVCR70.DLL, MSVCR71.DLL, MSVCP110.DLL, etc.). Applications are required to install the appropriate version,<ref>{{cite web\|url=http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.71).aspx\|archive-url=https://web.archive.org/web/20111207093317/http://msdn.microsoft.com/en-us/library/abx4dbyh(VS.71).aspx\|archive-date=2011-12-07\|title=C Run-Time Libraries\|access-date=2011-12-14}}</ref> and Microsoft offers '''Visual C++ Redistributable''' packages for this purpose, though Windows typically comes with one version already installed. This runtime library is used by programs written in Visual C++ and a few other compilers (e.g. [[MinGW]]). Some compilers have their own runtime libraries.

Microsoft Windows library files: Difference between revisions