Historically, the CRT in Visual Studio was a monolithic block. In 2013, Microsoft began the process of modularizing the runtime. This was a strategic move to support the Windows Store app model, but it had profound benefits for desktop developers as well. It improved load times and reduced memory footprints by allowing the operating system to share more code pages between processes.
Why does Visual C++ 2013 matter today? In 2024, we are writing code that can be compiled by five different compilers across three operating systems. We take auto , lambdas, and smart pointers for granted.
Perhaps most importantly for the standard library enthusiasts, VC++ 2013 implemented the C++11 threading model more robustly than its predecessors. While 2012 introduced std::thread , 2013 refined the mutexes, condition variables, and thread-local storage. It was the first time a Windows developer could write standard-compliant multithreaded code and trust that it would behave identically on Linux. 2013 visual c++
This refactor also addressed the "DLL Hell" of the Visual C++ Redistributables. While not fully solved until later versions, 2013 laid the groundwork for the app-local deployment models we use today, where applications ship with their specific version of the runtime, isolated from system-wide changes.
The most significant arrival was . Before 2013, Windows developers writing template-heavy code had to rely on ugly preprocessor macros or strict limits on argument counts. Variadic templates unlocked the ability to write true generic code, paving the way for sophisticated type-safe libraries. It was the moment the C++ type system on Windows became as flexible as its Unix counterparts. Historically, the CRT in Visual Studio was a
| Component | Requirement | |-----------|--------------| | | Windows 7 or later (Windows 8/8.1, Windows Server 2012) | | Architecture | x86 and x64 | | RAM | 1 GB (2 GB recommended) | | Disk space | Up to 10 GB | | Target OS support | Windows Vista, 7, 8, 8.1, Windows Server 2008+, Windows XP SP3 (via v120_xp) |
But the codebases we maintain—the infrastructure running banks, the engines running AAA games, the firmware in industrial machines—often still bear the fingerprints of VC++ 2013. It was the compiler that stabilized the chaotic early days of C++11. It was the tool that allowed a generation of Windows developers to transition from "C with Classes" to "Modern C++" without breaking their build systems. It improved load times and reduced memory footprints
Note: Visual C++ 2013 was the to officially support Windows XP as a target platform.