Microsoft C++ porting and upgrading guide
This article provides a guide for upgrading Microsoft C++ code to the latest version of Visual Studio. For projects created in Visual Studio 2010 through 2017, just open the project in Visual Studio 2019. You can upgrade a Visual Studio 2008 or earlier project in two steps. Use Visual Studio 2010 to convert the project to MSBuild format first. Then open the project in Visual Studio 2019. For complete instructions, see Upgrading C++ projects from earlier versions of Visual Studio.
The toolsets in Visual Studio 2015, Visual Studio 2017, and Visual Studio 2019 are binary-compatible. Now you can upgrade to a more recent version of the compiler without having to upgrade your library dependencies. For more information, see C++ binary compatibility between Visual Studio versions.
When upgrading projects that use open-source libraries or are meant to run on multiple platforms, we recommended migrating to a CMake-based project. For more information, see CMake projects in Visual Studio
Reasons to upgrade C++ code
If a legacy application is running satisfactorily, in a secure environment, and isn't under active development, there might not be much incentive to upgrade it. However, consider an upgrade in these cases: Your application requires ongoing maintenance. Or, you're doing new feature development, or making performance or security improvements. An upgrade brings these benefits:
The same code can run faster, because we've improved compiler optimizations.
Modern C++ features and programming practices eliminate many common causes of bugs, and produce code that's far easier to maintain than older C-style idioms.
Build times are faster, because of performance improvements in the compiler and linker.
Multitargeting vs. upgrading
Perhaps upgrading your code base to a new toolset isn't an option for you. You can still use the latest Visual Studio to build and edit projects that use older toolsets and libraries. In Visual Studio 2019, you can take advantage of features such as:
modern static analysis tools, including the C++ Core Guidelines checkers and Clang-Tidy, to help identify potential problems in your source code.
automatic formatting according to your choice of modern styles can help make legacy code much more readable.
For more information, see Use native multi-targeting in Visual Studio to build old projects.
In this section
|Upgrading C++ projects from earlier versions of Visual Studio||How to upgrade your code base to the latest version of Visual Studio and the compiler.|
|IDE tools for upgrading C++ code||Useful IDE features that help in the upgrade process.|
|C++ binary compatibility between Visual Studio versions||Consume v140 and later libraries as-is from v140 and later projects.|
|Use native multi-targeting in Visual Studio to build old projects||Use Visual Studio with older compilers and libraries.|
|Visual C++ change history 2003 - 2015||A list of all the changes in the Microsoft C++ libraries and build tools from Visual Studio 2003 through 2015 that might require changes in your code.|
|Visual C++ What's New 2003 through 2015||All the "what's new" information for Microsoft C++ from Visual Studio 2003 through Visual Studio 2015.|
|Porting and Upgrading: Examples and Case Studies||For this section, we ported and upgrades several samples and applications and discussed the experiences and results. These articles give you a sense of what's involved in the porting and upgrading process. Throughout the process, we discuss tips and tricks for upgrading and show how specific errors were fixed.|
|Porting to the Universal Windows Platform||Contains information about porting app code to Windows 10 and later|
|Introduction to Visual C++ for UNIX Users||Provides information for UNIX users who are new to Visual C++ and want to become productive with it.|
|Running Linux programs on Windows||Discusses options for migrating UNIX applications to Windows.|
Submit and view feedback for