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
Copy file name to clipboardExpand all lines: docs/porting/upgrading-projects-from-earlier-versions-of-visual-cpp.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,23 +17,23 @@ If you choose **Yes**, then the project gets converted. It can't be converted ba
17
17
18
18
When you upgrade a project, you get an upgrade report. The report is also saved in your project folder as UpgradeLog.htm. The upgrade report shows a summary of what problems were found during conversion. It lists some information about changes that were made, including:
19
19
20
-
1. Project properties.
20
+
- Project properties.
21
21
22
-
1. Include files.
22
+
- Include files.
23
23
24
-
1. Code that no longer compiles cleanly due to compiler conformance improvements or changes in the standard.
24
+
- Code that no longer compiles cleanly due to compiler conformance improvements or changes in the standard.
25
25
26
-
1. 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.
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
-
1. 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 due to changes in APIs such as renamed APIs, changed function signatures, or deprecated functions.
29
29
30
-
1. Code that no longer compiles because of changes in diagnostics, such as a warning becoming an error
30
+
- Code that no longer compiles because of changes in diagnostics, such as a warning becoming an error
31
31
32
-
1. Linker errors due to libraries that were changed, especially when /NODEFAULTLIB is used.
32
+
- Linker errors due to libraries that were changed, especially when /NODEFAULTLIB is used.
33
33
34
-
1. Runtime errors or unexpected results because of behavior changes.
34
+
- Runtime errors or unexpected results because of behavior changes.
35
35
36
-
1. Errors that were introduced in the tools. If you find an issue, report it to the Visual C++ team through your normal support channels or by using the [Visual Studio C++ Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html) page.
36
+
- Errors that were introduced in the tools. If you find an issue, report it to the Visual C++ team through your normal support channels or by using the [Visual Studio C++ Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html) page.
37
37
38
38
Some upgraded projects and solutions can be built successfully without modification. However, most projects will likely require changes to both project settings and your source code. There's no single correct way to go about fixing these issues, but we recommend using a phased approach. Before you start, review [Overview of potential upgrade issues](../porting/overview-of-potential-upgrade-issues-visual-cpp.md) for more information on many kinds of common errors.
39
39
@@ -47,7 +47,7 @@ Some upgraded projects and solutions can be built successfully without modificat
47
47
48
48
1. Fix any remaining errors that prevent compilation. Refer to [Overview of potential upgrade issues](../porting/overview-of-potential-upgrade-issues-visual-cpp.md) for fixes for common errors.
49
49
50
-
1. Turn **permissive-** back on and fix any new errors caused by non-conformant code that previously compiled in MSVC.
50
+
1. Turn **/permissive-** back on and fix any new errors caused by non-conformant code that previously compiled in MSVC.
51
51
52
52
1. Turn on code analysis to identify potential problems or outdated coding patterns that are no longer considered acceptable. If code analysis flags many errors, you can turn off some of the warnings to focus on the most important ones first. The IDE can help with Quick Fixes for some kinds of issues.
0 commit comments