Visual C++ Porting and Upgrading Guide
This topic provides a guide for upgrading Visual C++ code. This includes getting the code to compile and run correctly on a newer release of the tools, as well as taking advantage of new language and Visual Studio features. This topic also includes information about migrating legacy apps to more modern platforms.
Reasons to Upgrade Visual C++ Code
You should consider upgrading your code for the following reasons:
Faster code, due to improved compiler optimizations.
Faster builds, due to performance improvements in the compiler itself.
Improved standards conformance. Visual C++ now implements many features from the latest C++ standards.
Better security. Security features such as guard checking.
Porting your Code
When upgrading, first consider your application's code and projects. Is your application built with Visual Studio? If so, identify the projects involved. Do you have custom build scripts? If you have custom build scripts instead of using Visual Studio's build system, you will have more work to do in upgrading, because you can't save time by having Visual Studio update your project files and build settings.
The build system and project file format in Visual Studio changed from vcbuild in versions up to Visual Studio 2008 to MSBuild in versions of Visual Studio from 2010 onwards. If your upgrade is from a version prior to 2010, and you have a highly customized build system, you might have to do more work to upgrade. If you are upgrading from Visual Studio 2010 or later, your projects are already using MSBuild, so upgrading the project and build for your application should be easier.
If you are not using Visual Studio's build system, you should consider upgrading to use MSBuild. If you upgrade to use MSBuild, you might have an easier time in future upgrades, and it will be easier to use services such as Visual Studio Online. MSBuild supports all the target platforms that Visual Studio supports.
Porting Visual Studio Projects
To start upgrading a project or solution, just open the solution in the new version of Visual Studio, and follow the prompts to start upgrading it. When you upgrade a project, you get an upgrade report, which is also saved in your project folder as UpgradeLog.htm. The upgrade report shows a summary of what problems were encountered during the upgrade process and some information about changes that were made, or problems that could not be addressed automatically.
Code that no longer compiles cleanly due to compiler conformance imrovements or changes in the standard
Code that relies on Visual Studio or Windows features that are no longer available or header files that either aren't included in a default installation of Visual Studio, or were removed from the product
Code that no longer compiles due to changes in APIs such as renamed APIs, changed function signatures, or deprecated functions
Code that no longer compiles due to changes in diagnostics, such as warning becoming an error
Linker errors due to libraries that were changed, especially when /NODEFAULTLIB is used.
Runtime errors or unexpected results due to behavior changes
Errors due to errors that were introduced in the tools. If you encounter an issue, report it to the Visual C++ team through your normal support channels or by using the Visual Studio Feedback Center.
In addition to changes that you can't avoid due to compiler errors, some changes are optional in an upgrade process, such as:
New warnings might mean you want to clean up your code. Depending on the specific diagnostics, this can improve the portability, standards conformance, and security of your code.
You might want to take advantage of newer compiler features such as the /guard:cf (Enable Flow Control Guard) compiler option, which adds checks for unauthorized code execution.
You might want to update some code to use new language features that simplify the code, improve the performance of your programs, or update the code to use modern libraries and conform to modern standards and best practices.
Once you've upgraded and tested your project, you might also want to consider improving your code further or plan the future direction of your code, or even reconsider the architecture of your project. Will it receive ongoing development work? Will it be important for your code to run on other platforms? If so, what platforms? C++ is a standardized langauge designed with portability and cross-platform development in mind, and yet the code for many Windows applications is strongly tied to the Windows platform. Do you want to refactor your code, to separate out those parts that are more tied to the Windows platform?
What about your user interface? If you are using MFC, you might want to update the UI. Are you using any of the newer MFC features that were introduced in 2008 as a Feature Pack? If you just want to give your app a newer look and feel, without rewriting the entire app, you might consider using the ribbon APIs in MFC, or using some of new features of MFC.
If you want to give your program a XAML user-interface but don't want to create a UWP app, you can use C# with WPF to create the UI layer and refactor your standard C++ logic into DLLs. Create an interoperability layer in C++/CLI to connect C# with your native code. Another option is to create a UWP app using C++/CX or C++/WinRT. In Windows 10, you can use the Desktop App Converter to package your existing desktop application as a UWP app without having to modify any code.
Alternatively, perhaps you now have new requirements, or you can foresee the need for targeting platforms other than Windows desktop, such as Windows Phone, or Android devices. You could port your user interface code to a cross-platform UI library. With these UI frameworks, you can target multiple devices and still use Visual Studio and the Visual Studio debugger as your development environment.
|Upgrading Projects from Earlier Versions of Visual C++||Discusses how to use projects created in earlier versions of Visual C++.|
|What's New for The C++ compiler in Visual Studio 2017 RC||Changes in the IDE and tools from Visual Studio 2015 to Visual Studio 2017|
|C++ conformance improvements in Visual Studio 2017||Standards conformance improvements from Visual Studio 2015 to Visual Studio 2017|
|Visual C++ change history 2003 - 2015||A list of all the changes in the Visual 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 Visual C++ from Visual Studio 2003 through Visual Studio 2015.|
|Porting 3rd-party libraries||How to use the vcpkg command line tool to port older open-source libraries to versions compiled with more recent Visual C++ toolsets.|
|Porting and Upgrading: Examples and Case Studies||For this section, we ported and upgrades several samples and applications and discussed the experiences and results. You might find that reading these gives you a sense of what is 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 code to Windows 10|
|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.|
|Porting from UNIX to Win32||Discusses options for migrating UNIX applications to Windows.|
|C++/CLI Migration Primer||Shows in detail how to upgrade your Managed Extensions for C++ syntax to use the new syntax. For more information, see Component Extensions for Runtime Platforms.|