Merge pull request #3402 from MicrosoftDocs/master

2/9 AM Publish

Author: v-alje

.whatsnew.json

@@ -15,30 +15,30 @@
     "omitPullRequestTitles": false
   },
   "areas": [
-      {"names": ["assembler", "intrinsics"], "heading": "Microsoft C/C++ compiler intrinsics and assembly language"},
+      {"names": ["assembler", "intrinsics"], "heading": "C/C++ compiler intrinsics and assembly language"},
       {"names": ["atl", "atl-mfc-shared", "mfc"], "heading": "Active Template Library (ATL), Microsoft Foundation Classes (MFC)"},
-      {"names": ["build"], "heading": "Microsoft C++ in Visual Studio projects and build systems"},
+      {"names": ["build"], "heading": "C/C++ projects and build systems"},
       {"names": ["build-insights"], "heading": "Build insights"},
       {"names": ["c-language"], "heading": "C language"},
       {"names": ["cloud"], "heading": "Cloud programming with Microsoft C++"},
       {"names": ["code-quality"], "heading": "Code quality"},
-      {"names": ["cpp"], "heading": "Microsoft C++ in Visual Studio"},
+      {"names": ["cpp"], "heading": "C++ in Visual Studio"},
       {"names": ["cppcx"], "heading": "C++ /CX"},
       {"names": ["cross-platform"], "heading": "Cross platform development"},
       {"names": ["c-runtime-library"], "heading": "C runtime library"},
-      {"names": ["data"], "heading": "Data access in Microsoft C/C++ in Visual Studio"},
+      {"names": ["data"], "heading": "Data access in C/C++ in Visual Studio"},
       {"names": ["dotnet"], "heading":"STL/CLR library reference"},
-      {"names": ["error-messages"], "heading":"Microsoft C/C++ compiler and tools errors and warnings"},
+      {"names": ["error-messages"], "heading":"C/C++ compiler and tools errors and warnings"},
       {"names": ["extensions"], "heading":"Component extensions for .NET and UWP"},
-      {"names": ["get-started"], "heading":"Microsoft C++ in Visual Studio tutorials"},
-      {"names": ["ide"], "heading":"Read and write code using Microsoft C++ in Visual Studio"},
-      {"names": ["linux"], "heading":"Linux with Microsoft C++ in Visual Studio"},
-      {"names": ["overview"], "heading":"Microsoft C/C++ in Visual Studio overview"},
-      {"names": ["parallel"], "heading":"Parallel programming in Microsoft C++ in Visual Studio"},
-      {"names": ["porting"], "heading":"Microsoft C++ porting and upgrade guide"},
+      {"names": ["get-started"], "heading":"C++ in Visual Studio tutorials"},
+      {"names": ["ide"], "heading":"Read and write code using C++ in Visual Studio"},
+      {"names": ["linux"], "heading":"Linux with C++ in Visual Studio"},
+      {"names": ["overview"], "heading":"C/C++ in Visual Studio overview"},
+      {"names": ["parallel"], "heading":"Parallel programming in C++ in Visual Studio"},
+      {"names": ["porting"], "heading":"C++ porting and upgrade guide"},
       {"names": ["preprocessor"], "heading":"C/C++ preprocessor reference"},
       {"names": ["safeint", "security"], "heading":"Security best practices for C++"},
-      {"names": ["standard-library"], "heading":"Microsoft C++ Standard Template Library (STL) reference"},
+      {"names": ["standard-library"], "heading":"C++ Standard Template Library (STL) reference"},
       {"names": ["text"], "heading":"Text and strings in Visual Studio C++"},
       {"names": ["windows"], "heading":"Overview of Windows programming in C++"}    
       ]

docs/build/clang-support-msbuild.md

@@ -1,7 +1,7 @@
 ---
 description: "Learn more about: Clang/LLVM support in Visual Studio projects"
-title: "Clang/LLVM support in Visual Studio Visual Studio projects"
-ms.date: "06/02/2020"
+title: "Clang/LLVM support in Visual Studio projects"
+ms.date: 02/05/2021
 ms.description: "Configure a Visual Studio MSBuild project to use the Clang/LLVM toolchain."
 helpviewer_keywords: ["Clang support for C++ MSBuild projects"]
 ---
@@ -19,7 +19,9 @@ You can use Visual Studio 2019 version 16.2 with Clang to edit, build, and debug
 
 ## Install
 
-For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have those, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. If you prefer to use an existing Clang installation on your machine, choose the **C++ Clang-cl for v142 build tools.** optional component. The Microsoft C++ Standard Library currently requires at least Clang 8.0.0; the bundled version of Clang will automatically be updated to stay current with updates in the Microsoft implementation of the Standard Library.
+For best IDE support in Visual Studio, we recommend using the latest Clang compiler tools for Windows. If you don't already have the tools, you can install them by opening the Visual Studio Installer and choosing **C++ Clang tools for Windows** under **Desktop development with C++** optional components. You may prefer to use an existing Clang installation on your machine; if so, choose the **C++ Clang-cl for v142 build tools.** optional component.
+
+The Microsoft C++ Standard Library currently requires at least Clang 8.0.0. The bundled version of Clang gets updated automatically to stay current with updates in the Microsoft implementation of the Standard Library.
 
 ![Screenshot of the Visual Studio installer with the Individual components tab selected and the C plus plus Clang components visible.](media/clang-install-vs2019.png)
 
@@ -29,9 +31,9 @@ To configure a Visual Studio project to use Clang, right-click on the project no
 
 ![Screenshot of the Property Pages dialog box with Configuration Properties > General selected and the Platform Toolset and L L V M (clang c l) options highlighted.](media/clang-msbuild-prop-page.png)
 
-If you are using the Clang tools that are bundled with Visual Studio, no additional steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode and links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in *%VCINSTALLDIR%\\Tools\\Llvm\\bin\\* and *%VCINSTALLDIR%\\Tools\\Llvm\\x64\\bin\\*.
+If you're using the Clang tools that are bundled with Visual Studio, no extra steps are required. For Windows projects, Visual Studio by default invokes Clang in [clang-cl](https://llvm.org/devmtg/2014-04/PDFs/Talks/clang-cl.pdf) mode. It links with the Microsoft implementation of the Standard Library. By default, **clang-cl.exe** is located in *%VCINSTALLDIR%\\Tools\\Llvm\\bin\\* and *%VCINSTALLDIR%\\Tools\\Llvm\\x64\\bin\\*.
 
-If you are using a custom Clang installation, you can either modify **Project** > **Properties** > **VC++ DIrectories** > **Configuration Properties** > **Executable Directories** by adding the custom Clang installation root as the first directory there, or change the value of the `LLVMInstallDir` property. See [Set a custom LLVM location](#custom_llvm_location) for more information.
+If you're using a custom Clang installation, you can either modify **Project** > **Properties** > **VC++ DIrectories** > **Configuration Properties** > **Executable Directories** by adding the custom Clang installation root as the first directory there, or change the value of the `LLVMInstallDir` property. For more information, see [Set a custom LLVM location](#custom_llvm_location).
 
 ## Configure a Linux project to use Clang tools
 
@@ -41,28 +43,69 @@ To configure a Visual Studio Linux project to use Clang:
 
 1. Right-click on the project node in **Solution Explorer** and choose **Properties**.
 1. Typically, you should first choose **All configurations** at the top of the dialog.
-1. Under **General** > **Platform Toolset**, choose **WSL_Clang_1_0** if you are using Windows Subsystem for Linux, or **Remote_Clang_1_0** if you are using a remote machine or VM.
+1. Under **General** > **Platform Toolset**, choose **WSL_Clang_1_0** if you're using Windows Subsystem for Linux (WSL). Choose **Remote_Clang_1_0** if you're using a remote machine or VM.
 1. Press **OK**.
 
 ![Screenshot of the Console App clang Visual Studio 2019 Property Pages dialog box with Configuration Properties > General selected and the Platform Toolset and L L V M (clang c l) options highlighted.](media/clang-msbuild-prop-page.png)
 
-On Linux, Visual Studio by default uses the first Clang location that it encounters in the PATH environment property. If you are using a custom Clang installation, then you must change the value of the `LLVMInstallDir` property or else substitute a path under **Project** > **Properties** > **VC++ DIrectories** > **Configuration Properties** > **Executable Directories**. See [Set a custom LLVM location](#custom_llvm_location) for more information.
+On Linux, Visual Studio by default uses the first Clang location that it finds in the PATH environment property. If you're using a custom Clang installation, then either change the value of the `LLVMInstallDir` property or else enter the path under **Project** > **Properties** > **Configuration Properties** > **VC++ DIrectories** > **Executable Directories**. For more information, see [Set a custom LLVM location](#custom_llvm_location).
 
 ## <a name="custom_llvm_location"></a> Set a custom LLVM location
 
-You can set a custom path for LLVM for one or more projects by creating a *Directory.build.props* file and adding that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but substitute your actual path):
+You can set a custom path to LLVM for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. You can add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path):
 
 ```xml
 <Project>
   <PropertyGroup>
-    <LLVMInstallDir>c:\MyLLVMRootDir</LLVMInstallDir>
+    <LLVMInstallDir>C:\MyLLVMRootDir</LLVMInstallDir>
   </PropertyGroup>
 </Project>
 ```
 
+You can combine this property with a custom LLVM toolset version. For more information, see [Set a custom LLVM toolset version](#custom_llvm_toolset).
+
+## <a name="custom_llvm_toolset"></a> Set a custom LLVM toolset version
+
+Starting in Visual Studio 2019 version 16.9, you can set a custom toolset version for LLVM. To set this property in a project in Visual Studio:
+
+1. Open the project's **Property Pages** dialog box. For details, see [Set C++ compiler and build properties in Visual Studio](./working-with-project-properties.md).
+
+1. Select the **Configuration Properties** > **General** property page.
+
+1. Modify the **Platform Toolset** property to *LLVM (clang-cl)*, if it isn't already set.
+
+1. Select the **Configuration Properties** > **Advanced** property page.
+
+1. Modify the **LLVM Toolset Version** property to your preferred version, and then choose **OK** to save your changes.
+
+The **LLVM Toolset Version** property only appears when the LLVM platform toolset is selected.
+
+You can set the toolset version for one or more projects by creating a *Directory.build.props* file. Then, add that file to the root folder of any project. Add it to the root solution folder to apply it to all projects in the solution. The file should look like this (but use your actual LLVM path):
+
+```xml
+<Project>
+  <PropertyGroup>
+    <LLVMToolsVersion>11.0.0</LLVMToolsVersion>
+  </PropertyGroup>
+</Project>
+```
+
+You can also combine this property with a custom LLVM location. For example, your *Directory.build.props* file could look like:
+
+```xml
+<Project>
+  <PropertyGroup>
+    <LLVMInstallDir>C:\MyLLVMRootDir</LLVMInstallDir>
+    <LLVMToolsVersion>11.0.0</LLVMToolsVersion>
+  </PropertyGroup>
+</Project>
+```
+
+When you add a *Directory.build.props* file, the settings appear as the default in the project Property Pages dialog. However, changes to these properties in Visual Studio override the settings in the *Directory.build.props* file.
+
 ## Set additional properties, edit, build, and debug
 
-After you have set up a Clang configuration, right-click again on the project node and choose **Reload project**. You can now build and debug the project using the Clang tools. Visual Studio detects that you are using the Clang compiler and provides IntelliSense, highlighting, navigation, and other editing features. Errors and warnings are displayed in the **Output Window**. The project property pages for a Clang configuration are very similar to those for MSVC, although some compiler-dependent features such as Edit and Continue are not available for Clang configurations. To set a Clang compiler or linker option that is not available in the property pages, you can add it manually in the property pages under **Configuration Properties** > **C/C++ (or Linker)** > **Command Line** > **Additional Options**.
+After you have set up a Clang configuration, right-click again on the project node and choose **Reload project**. You can now build and debug the project using the Clang tools. Visual Studio detects that you're using the Clang compiler and provides IntelliSense, highlighting, navigation, and other editing features. Errors and warnings are displayed in the **Output Window**. The project property pages for a Clang configuration are similar to the ones for MSVC. However, some compiler-dependent features such as Edit and Continue aren't available for Clang configurations. You can set a Clang compiler or linker option that isn't available in the property pages. Add it manually in the property pages under **Configuration Properties** > **C/C++ (or Linker)** > **Command Line** > **Additional Options**.
 
 When debugging, you can use breakpoints, memory and data visualization, and most other debugging features.  
 

docs/build/reference/advanced-property-page.md

@@ -1,8 +1,8 @@
 ---
 description: "Learn more about: Advanced Property Page"
 title: "Advanced Property Page (Project)"
-ms.date: 08/10/2020
-f1_keywords: ["VC.Project.VCConfiguration.VCToolsVersion"]
+ms.date: 02/05/2021
+f1_keywords: ["VC.Project.VCConfiguration.VCToolsVersion","VC.Project.VCConfiguration.LLVMToolsVersion"]
 ms.description: "Use the Advanced property page in Visual Studio 2019 to set various properties for C++ projects."
 ---
 # Advanced Property Page
@@ -83,6 +83,10 @@ The Advanced property page is available in Visual Studio 2019 and later.
 
    Specifies the full version of the MSVC toolset that's used to build the project. You may have various update and preview versions of a toolset installed. You can specify which one to use here.
 
+- **LLVM Toolset Version**
+
+   Specifies the full version of the LLVM toolset that's used to build the project. This property is available when **LLVM (clang-cl)** is selected as the platform toolset, starting in Visual Studio 2019 version 16.9. For more information, see [Set a custom LLVM toolset version](..\clang-support-msbuild.md#custom_llvm_toolset).
+
 ## C++/CLI Properties
 
 - **Common Language Runtime support**

docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md

@@ -1,16 +1,17 @@
 ---
 title: "What's new for C++ in Visual Studio"
 description: "The new features and fixes in the Microsoft C/C++ compiler and tools in Visual Studio."
-ms.date: "05/19/2020"
+ms.date: "02/08/2021"
 ms.technology: "cpp-ide"
-ms.assetid: 8801dbdb-ca0b-491f-9e33-01618bff5ae9
 ---
 # What's new for C++ in Visual Studio
 
 ::: moniker range=">=msvc-160"
 
 Visual Studio 2019 brings many updates and fixes to the Microsoft C++ environment. We've fixed many bugs and issues in the compiler and tools. Many of these issues were submitted by customers through the [Report a Problem](/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2019&preserve-view=true) and [Provide a Suggestion](https://aka.ms/feedback/suggest?space=62) options under **Send Feedback**. Thank you for reporting bugs! For more information on what's new in all of Visual Studio, visit [What's new in Visual Studio 2019](/visualstudio/ide/whats-new-visual-studio-2019). For information on what's new for C++ in Visual Studio 2017, see [What's new for C++ in Visual Studio 2017](?preserve-view=true&view=msvc-150). 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).
+
 ## C++ compiler
 
 - Enhanced support for C++17 features and correctness fixes, plus experimental support for C++20 features such as modules and coroutines. For detailed information, see [C++ Conformance Improvements in Visual Studio 2019](cpp-conformance-improvements.md).

docs/overview/whats-new-cpp-docs.md

@@ -1,11 +1,15 @@
 ---
 title: "What's new for the C++ docs"
 description: "The new docs and doc updates for the Microsoft C/C++ compiler, ATL/MFC, C runtime, and standard library docs."
-ms.date: "02/05/2021"
+ms.date: "02/08/2021"
 ---
 # Microsoft C++ docs: What's new for Visual Studio 16.8
 
-This article lists some of the major changes to docs for Visual Studio 16.8.
+This article lists some of the major changes to docs for Visual Studio 16.8. 
+
+For information about what's new in Visual Studio, see [What's new for C++ in Visual Studio](what-s-new-for-visual-cpp-in-visual-studio.md).
+
+For the latest C++ conformance status, see [C++ conformance improvements in Visual Studio](cpp-conformance-improvements.md)
 
 ## C language
 
@@ -107,7 +111,7 @@ This article lists some of the major changes to docs for Visual Studio 16.8.
 - [Configure a Linux CMake project in Visual Studio](../linux/cmake-linux-configure.md) - Updated to reflect latest UI
 - [Deploy, run, and debug your Linux MSBuild project](../linux/deploy-run-and-debug-your-linux-project.md) - Added `GDB Path`
 
-## Microsoft C/C++ compiler and tools errors and warnings
+## C/C++ compiler and tools errors and warnings
 
 ### New articles
 
@@ -121,7 +125,7 @@ This article lists some of the major changes to docs for Visual Studio 16.8.
 - [Compiler warnings C4800 through C5999](../error-messages/compiler-warnings/compiler-warnings-c4800-through-c4999.md) - Updated 16.7 warnings
 - [Compiler Error C3381](../error-messages/compiler-errors-2/compiler-error-c3381.md) - Address cpp-docs 2493; update remarks and example
 
-## Microsoft C/C++ compiler intrinsics and assembly language
+## C/C++ compiler intrinsics and assembly language
 
 ### Updated articles
 
@@ -130,15 +134,15 @@ This article lists some of the major changes to docs for Visual Studio 16.8.
 - [C++ in Visual Studio](../overview/visual-cpp-in-visual-studio.md) - Updated DevCom and Microsoft Docs Q&A links
 - [Microsoft C++ language conformance table](../overview/visual-cpp-language-conformance.md) - Updated C++20 library conformance table, update language feature table for 16.7
 
-## Microsoft C++ in Visual Studio
+## C++ in Visual Studio
 
 ### Updated articles
 
 - [`__restrict`](../cpp/extension-restrict.md)
 - [if-else statement (C++)](../cpp/if-else-statement-cpp.md) - Added description for `if/else` grammar
 - [`union`](../cpp/unions.md) - Fixed code snippet
 
-## Microsoft C++ in Visual Studio projects and build systems
+## C/C++ projects and build systems
 
 ### New articles
 
@@ -155,13 +159,14 @@ This article lists some of the major changes to docs for Visual Studio 16.8.
 - [`/clr` (Common Language Runtime Compilation)](../build/reference/clr-common-language-runtime-compilation.md) - Added description for `/clr`
 - [pgosweep](../build/pgosweep.md) - Added more pgosweep options
 - [Importing data using `__declspec(dllimport)`](../build/importing-data-using-declspec-dllimport.md) - Updated example
-## Microsoft C++ porting and upgrade guide
+
+## C++ porting and upgrade guide
 
 ### Updated articles
 
 - [How to: Use existing C++ code in a Universal Windows Platform app](../porting/how-to-use-existing-cpp-code-in-a-universal-windows-platform-app.md) - Reworked for clarity and updated examples
 
-## Microsoft C++ Standard Library (STL) reference
+## C++ Standard Library (STL) reference
 
 ### New articles