Skip to content

Commit 79ace4f

Browse files
author
3836425+corob-msft@users.noreply.github.com
committed
VS2022 update for what's new content
1 parent c164c8c commit 79ace4f

13 files changed

Lines changed: 681 additions & 551 deletions

‎docs/build/reference/std-specify-language-standard-version.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "/std (Specify Language Standard Version)"
33
description: "The MSVC compiler option /std specifies the C or C++ language standard supported by the compiler."
4-
ms.date: 06/14/2021
4+
ms.date: 10/22/2021
55
f1_keywords: ["/std", "-std", "/std:c++14", "/std:c++17", "/std:c11", "/std:c17", "VC.Project.VCCLCompilerTool.CppLanguageStandard"]
66
---
77
# `/std` (Specify Language Standard Version)
@@ -51,7 +51,7 @@ The **`/std:c++20`** option disables compiler and standard library support for f
5151
**`/std:c++latest`**\
5252
The **`/std:c++latest`** option enables all currently implemented compiler and standard library features proposed for the next draft standard, as well as some in-progress and experimental features. This option is available starting in Visual Studio 2015 Update 3.
5353

54-
Depending on the MSVC compiler version or update level, C++17 or C++20 features may not be fully implemented or fully conforming when you specify the **`/std:c++latest`** option. For an overview of C++ language conformance in Visual C++ by release version, see [Microsoft C/C++ language conformance](../../overview/visual-cpp-language-conformance.md).
54+
Depending on the MSVC compiler version or update level, C++17, C++20, or proposed C++23 features may not be fully implemented or fully conforming when you specify the **`/std:c++latest`** option. We recommend you use the latest version of Visual Studio for maximum standards conformance. For an overview of C++ language and library conformance in Visual C++ by release version, see [Microsoft C/C++ language conformance](../../overview/visual-cpp-language-conformance.md).
5555

5656
In versions of Visual Studio 2019 before version 16.11, **`/std:c++latest`** is required to enable all the compiler and standard library features of C++20.
5757

‎docs/error-messages/compiler-errors-1/fatal-error-c1047.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: "Learn more about: Fatal Error C1047"
33
title: "Fatal Error C1047"
4-
ms.date: 02/17/2021
4+
ms.date: 10/22/2021
55
f1_keywords: ["C1047"]
66
helpviewer_keywords: ["C1047"]
77
---
@@ -21,4 +21,4 @@ To resolve C1047, rebuild all object files or libraries by using the same versio
2121

2222
[`/GL` (Whole Program Optimization)](../../build/reference/gl-whole-program-optimization.md)\
2323
[`/LTCG` (Link-time code generation)](../../build/reference/ltcg-link-time-code-generation.md)\
24-
[C++ binary compatibility 2015-2019](../../porting/binary-compat-2015-2017.md)
24+
[C++ binary compatibility between Visual Studio versions](../../porting/binary-compat-2015-2017.md)

‎docs/error-messages/tool-errors/linker-tools-error-lnk2001.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
description: "Learn more about: Linker Tools Error LNK2001"
33
title: "Linker Tools Error LNK2001"
4-
ms.date: "12/19/2019"
4+
ms.date: 10/22/2021
55
f1_keywords: ["LNK2001"]
66
helpviewer_keywords: ["LNK2001"]
77
ms.assetid: dc1cf267-c984-486c-abd2-fd07c799f7ef
@@ -36,7 +36,7 @@ This error can occur:
3636

3737
- If you link to the release mode libraries when building a debug version of an application. Similarly, if you use options **/MTd** or **/MDd** or define `_DEBUG` and then link to the release libraries, you should expect many potential unresolved externals, among other problems. Linking a release mode build with the debug libraries also causes similar problems. To fix this issue, make sure you use the debug libraries in your debug builds, and retail libraries in your retail builds.
3838

39-
- If your code refers to a symbol from one library version, but you link a different version of the library. Generally, you can't mix object files or libraries that are built for different versions of the compiler. The libraries that ship in one version may contain symbols that can't be found in the libraries included with other versions. To fix this issue, build all the object files and libraries with the same version of the compiler before linking them together. For more information, see [C++ binary compatibility 2015-2019](../../porting/binary-compat-2015-2017.md).
39+
- If your code refers to a symbol from one library version, but you link a different version of the library. Generally, you can't mix object files or libraries that are built for different versions of the compiler. The libraries that ship in one version may contain symbols that can't be found in the libraries included with other versions. To fix this issue, build all the object files and libraries with the same version of the compiler before linking them together. For more information, see [C++ binary compatibility between Visual Studio versions](../../porting/binary-compat-2015-2017.md).
4040

4141
- If library paths are out of date. The **Tools > Options > Projects > VC++ Directories** dialog, under the **Library files** selection, allows you to change the library search order. The Linker folder in the project's Property Pages dialog box may also contain paths that could be out of date.
4242

‎docs/overview/toc.yml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,10 @@ items:
66
href: ../overview/visual-cpp-in-visual-studio.md
77
- name: Overview of C++ development in Visual Studio
88
href: ../overview/overview-of-cpp-development.md
9-
- name: What's new for C++ in Visual Studio 2019
9+
- name: What's new for C++ in Visual Studio 2022 Preview
1010
href: ../overview/what-s-new-for-visual-cpp-in-visual-studio.md
11+
- name: What's new for C++ in Visual Studio 2019
12+
href: ../overview/what-s-new-for-cpp-2019.md
1113
- name: What's new for C++ in Visual Studio 2017
1214
href: ../overview/what-s-new-for-cpp-2017.md
1315
- name: What's new for Microsoft C++ docs

‎docs/overview/visual-cpp-language-conformance.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "Microsoft C/C++ language conformance"
33
description: "Microsoft C and C++ conformance updates by Visual Studio version."
4-
ms.date: 06/22/2021
4+
ms.date: 10/22/2021
55
ms.technology: "cpp-language"
66
---
77
# Microsoft C/C++ language conformance by Visual Studio version
@@ -11,7 +11,7 @@ Standards conformance for the Microsoft C/C++ compiler in Visual Studio (MSVC) i
1111
For details on conformance improvements, see [C++ conformance improvements in Visual Studio](cpp-conformance-improvements.md). For a list of other changes, see [What's New for Visual C++ in Visual Studio](what-s-new-for-visual-cpp-in-visual-studio.md). For conformance changes in earlier versions, see [Visual C++ change history](../porting/visual-cpp-change-history-2003-2015.md) and [Visual C++ What's New 2003 through 2015](../porting/visual-cpp-what-s-new-2003-through-2015.md). For current news from the C++ team, visit the [C++ team blog](https://devblogs.microsoft.com/cppblog/).
1212

1313
> [!NOTE]
14-
> There are no binary breaking changes between Visual Studio 2015, Visual Studio 2017, and Visual Studio 2019. For more information, see [C++ binary compatibility between Visual Studio 2015, 2017, and 2019](../porting/binary-compat-2015-2017.md)
14+
> There are no binary breaking changes between Visual Studio 2015, 2017, 2019, and 2022. For more information, see [C++ binary compatibility between Visual Studio versions](../porting/binary-compat-2015-2017.md)
1515
1616
## C++ compiler features
1717

‎docs/overview/what-s-new-for-cpp-2017.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.custom: intro-whats-new
99

1010
Visual Studio 2017 brings many updates and fixes to the C++ environment. We've fixed over 250 bugs and reported issues in the compiler and tools. Many were submitted by customers through the [Report a Problem and Provide a Suggestion](/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2017&preserve-view=true) options under **Send Feedback**. Thank you for reporting bugs!
1111

12-
For more information on what's new in all of Visual Studio, see [What's new in Visual Studio 2017](/visualstudio/ide/whats-new-visual-studio-2017?view=vs-2017&preserve-view=true). For information on what's new for C++ in Visual Studio 2019, see [What's new for C++ in Visual Studio](what-s-new-for-visual-cpp-in-visual-studio.md?preserve-view=true&view=msvc-160). For information on what's new for C++ in Visual Studio 2015 and earlier versions, see [Visual C++ What's New 2003 through 2015](../porting/visual-cpp-what-s-new-2003-through-2015.md). For information about what's new in the C++ docs, see [Microsoft C++ docs: What's new](whats-new-cpp-docs.md).
12+
For more information on what's new in all of Visual Studio, see [What's new in Visual Studio 2017](/visualstudio/ide/whats-new-visual-studio-2017?view=vs-2017&preserve-view=true). For information on what's new for C++ in Visual Studio 2019, see [What's new for C++ in Visual Studio 2019](what-s-new-for-visual-cpp-in-visual-studio.md?preserve-view=true&view=msvc-160). For information on what's new for C++ in Visual Studio 2015 and earlier versions, see [Visual C++ What's New 2003 through 2015](../porting/visual-cpp-what-s-new-2003-through-2015.md). For information about what's new in the C++ docs, see [Microsoft C++ docs: What's new](whats-new-cpp-docs.md).
1313

1414
## Visual Studio 2017 C++ compiler
1515

0 commit comments

Comments
 (0)