Toolsets from older VS installations on your box are visible as platform toolsets in the latest IDE. This way, your projects also load in the previous version of the IDE in case you need to go back or you have teammates that have not yet upgraded to VS 2019 (this functionality is also known as project round-tripping). Loading your existing C++ projects into the IDE will not upgrade/change your project files. MSVC v140 (VS 2015.3) and MSVC v141 (VS 2017) Toolsets in the Visual Studio 2019 IDEĮven if you are not ready yet to move your project to the latest toolset (MSVC v142), you can still load your project in the Visual Studio 2019 IDE and continue to use your current older toolset. The Visual Studio Installer will let you manage installations of Visual Studio 20 from a central UI. This is a great way to try Visual Studio 2019 or adopt it for some of your projects.

You can install the latest version of Visual Studio on a computer that already has an earlier version installed and continue to use both versions in parallel with no interference. Regardless of the toolset you’re on, you get access to the full collection of OSS libraries available in Vcpkg.You can upgrade to the latest MSVC v142 (VS 2019) and maintain binary compatibility with any of your 3rd party libraries that haven’t migrated yet.You can continue building your C++ code with the MSVC v140 (VS 2015.3) or v141 (VS 2017) toolsets.You can install the latest IDE side-by-side with any older VS versions.This post captures the reasons why your upgrade to Visual Studio 2019 will be pain-free. We hope that you will find these new capabilities compelling and start your upgrade to Visual Studio 2019 soon.Īs you are considering this upgrade, rest assured that Visual Studio 2019 makes it distinctively easy to move your codebase from previous versions of Visual Studio. Visual Studio 2019 pushes the boundaries of individual and team productivity.

Visual c++ 2019