The period between 2019 and 2021 was pivotal for Microsoft’s C++ ecosystem. While the core compiler toolset is technically known as MSVC (Microsoft Visual C++), users most often encounter it through two distinct avenues: the Visual Studio IDE (for developers) and the Visual C++ Redistributable (for end-users).
This write-up clarifies the state of Visual C++ during this era, covering the release of Visual Studio 2019, the evolution of the compiler standards, and the ongoing necessity of the Redistributable packages.
When users search for "Visual C++ 2021," they are almost certainly looking for Visual Studio 2022. Released in November 2021, this marked a major milestone as the first 64-bit version of the Visual Studio IDE. microsoft visual c 2019 2021
While the IDE underwent a massive overhaul to handle larger projects without memory constraints, the underlying compiler toolset (MSVC v143) carried forward the legacy of 2019. Importantly, Microsoft ensured high compatibility between the two. Developers using Visual Studio 2022 can still target the v142 toolset (from 2019), ensuring that legacy codebases do not break when upgrading their development environment.
In 2020 and 2021, Microsoft brought AddressSanitizer to Windows. Originally a Clang/GCC tool, ASan catches memory errors (buffer overflows, use-after-free) at runtime. Integrating this into MSVC was a massive move toward creating safer, more secure C++ applications on Windows. The "2021" Context: Visual Studio 2022 When users
std::from_chars for floating-point, some parallel algorithms)co_await, co_yield, co_return), std::spanFor the average computer user, "Visual C++" usually refers to the Microsoft Visual C++ Redistributable Packages. These are runtime libraries required to run applications built with MSVC.
If you are looking for "Visual C++ 2021," you are likely looking for the latest security updates for the Visual C++ 2015-2022 Redistributable. ASan catches memory errors (buffer overflows
Prior to 2019, MSVC lagged behind Clang and GCC in C++17 conformance. Microsoft restructured its compiler backend (LLVM not adopted, but internal improvements made) and increased collaboration with the ISO C++ committee.
Because this runtime is so common, it can still break. Here are the most frequent error messages and how to fix them.
You have two easy methods to verify this specific component.