You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To upgrade a project created in an earlier version of Visual Studio, just open the project in the latest version of Visual Studio. Visual Studio offers to upgrade the project to the current schema.
11
11
12
-
If you choose **No**, the project doesn't get upgraded. You can still use the project in the newer version of Visual Studio, though. Just set your project properties to continue to target the older toolset. If you leave the older version of Visual Studio on your computer, its toolset is available in later versions. For example, if your project must continue to run on Windows XP, you can upgrade to Visual Studio 2019. You then specify the toolset as v141 or earlier in your project properties. For more information, see [Use native multi-targeting in Visual Studio to build old projects](use-native-multi-targeting.md).
12
+
If you choose **No**, the project doesn't get upgraded. For projects created in Visual Studio 2010 and later, you can still use the project in the newer version of Visual Studio. Just set your project properties to continue to target the older toolset. If you leave the older version of Visual Studio on your computer, its toolset is available in later versions. For example, if your project must continue to run on Windows XP, you can upgrade to Visual Studio 2019. You then specify the toolset as v141_xp or earlier in your project properties. For more information, see [Use native multi-targeting in Visual Studio to build old projects](use-native-multi-targeting.md).
13
13
14
-
If you choose **Yes**, then the project gets converted. It can't be converted back to the earlier version. In upgrade scenarios, that's why it's good practice to make a copy of the existing project and solution files.
14
+
If you choose **Yes**, then the project gets upgraded in place. It can't be converted back to the earlier version. In upgrade scenarios, that's why it's good practice to make a backup copy of the existing project and solution files.
15
15
16
16
## Upgrade reports
17
17
@@ -21,15 +21,15 @@ When you upgrade a project, you get an upgrade report. The report is also saved
21
21
22
22
- Include files.
23
23
24
-
- Code that no longer compiles cleanly due to compiler conformance improvements or changes in the standard.
24
+
- Code that no longer compiles cleanly because of compiler conformance improvements or changes in the standard.
25
25
26
26
- 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.
27
27
28
-
- Code that no longer compiles due to changes in APIs such as renamed APIs, changed function signatures, or deprecated functions.
28
+
- Code that no longer compiles because of changes in APIs such as renamed APIs, changed function signatures, or deprecated functions.
29
29
30
30
- Code that no longer compiles because of changes in diagnostics, such as a warning becoming an error
31
31
32
-
- Linker errors due to libraries that were changed, especially when /NODEFAULTLIB is used.
32
+
- Linker errors because of libraries that were changed, especially when /NODEFAULTLIB is used.
33
33
34
34
- Runtime errors or unexpected results because of behavior changes.
0 commit comments