Merging changes synced from https://github.com/MicrosoftDocs/cpp-docs-pr (branch live)

Author: opbld16

docs/build/vscpp-step-0-installation.md

@@ -1,8 +1,8 @@
 ---
 title: Install C and C++ support in Visual Studio
-description: "Install Visual Studio support for Visual C++"
+description: "Learn how to install Visual Studio with support for Microsoft C/C++ and related workloads."
 ms.custom: "mvc"
-ms.date: "04/02/2019"
+ms.date: 11/05/2020
 ms.topic: "tutorial"
 ms.devlang: "cpp"
 ms.assetid: 45138d70-719d-42dc-90d7-1d0ca31a2f54
@@ -40,22 +40,22 @@ For questions about running previous versions of Visual Studio side by side with
 
 ### Step 2 - Download Visual Studio
 
-Next, download the Visual Studio bootstrapper file. To do so, choose the following button, choose the edition of Visual Studio that you want, choose **Save**, and then choose **Open folder**.
+Next, download the Visual Studio bootstrapper file. To do so, choose the following button to go to the Visual Studio download page. Select the edition of Visual Studio that you want and choose the **Free trial** or **Free download** button.
 
  > [!div class="button"]
  > [Download Visual Studio](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2019+rc)
 
 ### Step 3 - Install the Visual Studio installer
 
-Run the bootstrapper file to install the Visual Studio Installer. This new lightweight installer includes everything you need to both install and customize Visual Studio.
+Run the bootstrapper file you downloaded to install the Visual Studio Installer. This new lightweight installer includes everything you need to both install and customize Visual Studio.
 
 1. From your **Downloads** folder, double-click the bootstrapper that matches or is similar to one of the following files:
 
    - **vs_community.exe** for Visual Studio Community
    - **vs_professional.exe** for Visual Studio Professional
    - **vs_enterprise.exe** for Visual Studio Enterprise
 
-   If you receive a User Account Control notice, choose **Yes**.
+   If you receive a User Account Control notice, choose **Yes** to allow the bootstrapper to run.
 
 1. We'll ask you to acknowledge the Microsoft [License Terms](https://visualstudio.microsoft.com/license-terms/) and the Microsoft [Privacy Statement](https://privacy.microsoft.com/privacystatement). Choose **Continue**.
 
@@ -137,15 +137,12 @@ For details on the disk space and operating system requirements, see [Visual Stu
 
 ### Download and install
 
-1. Download the latest Visual Studio 2017 installer for Windows.
-
-   > [!div class="nextstepaction"]
-   > [Install Visual Studio 2017 Community](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017)
+1. To download the latest Visual Studio 2017 installer for Windows, go to the Microsoft Visual Studio [Older downloads](https://www.visualstudio.com/vs/older-downloads/) page. Expand the **2017** section, and choose the **Download** button.
 
    >[!Tip]
-   > The Community edition is for individual developers, classroom learning, academic research, and open source development. For other uses, install [Visual Studio 2017 Professional](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017) or [Visual Studio 2017 Enterprise](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=button+cta&utm_content=download+vs2017).
+   > The Community edition is for individual developers, classroom learning, academic research, and open source development. For other uses, install Visual Studio 2017 Professional or Visual Studio 2017 Enterprise.
 
-1. Find the installer file you downloaded and run it. It may be displayed in your browser, or you may find it in your Downloads folder. The installer needs Administrator privileges to run. You may see a **User Account Control** dialog asking you to give permission to let the installer make changes to your system; choose **Yes**. If you're having trouble, find the downloaded file in File Explorer, right-click on the installer icon, and choose **Run as Administrator** from the context menu.
+1. Find the installer file you downloaded and run it. The downloaded file may be displayed in your browser, or you may find it in your Downloads folder. The installer needs Administrator privileges to run. You may see a **User Account Control** dialog asking you to give permission to let the installer make changes to your system; choose **Yes**. If you're having trouble, find the downloaded file in File Explorer, right-click on the installer icon, and choose **Run as Administrator** from the context menu.
 
    ![Download and install the Visual Studio Installer](media/vscpp-concierge-run-installer.gif "Download and install the Visual Studio Installer")
 
@@ -179,7 +176,7 @@ For details on the disk space and operating system requirements, see [Visual Stu
 
 ## Visual Studio 2015 Installation
 
-To install Visual Studio 2015, go to [Download older versions of Visual Studio](https://www.visualstudio.com/vs/older-downloads/). Run the setup program and choose **Custom installation** and then choose the C++ component. To add C and C++ support to an existing Visual Studio 2015 installation, click on the Windows Start button and type **Add Remove Programs**. Open the program from the results list and then find your Visual Studio 2015 installation in the list of installed programs. Double-click it, then choose **Modify** and select the Visual C++ components to install.
+To install Visual Studio 2015, go to the Microsoft Visual Studio [Older downloads](https://www.visualstudio.com/vs/older-downloads/) page. Expand the **2015** section, and choose the **Download** button. Run the downloaded setup program and choose **Custom installation** and then choose the C++ component. To add C and C++ support to an existing Visual Studio 2015 installation, click on the Windows Start button and type **Add Remove Programs**. Open the program from the results list and then find your Visual Studio 2015 installation in the list of installed programs. Double-click it, then choose **Modify** and select the Visual C++ components to install.
 
 In general, we highly recommend that you use the latest version of Visual Studio even if you need to compile your code using the Visual Studio 2015 compiler. For more information, see [Use native multi-targeting in Visual Studio to build old projects](../porting/use-native-multi-targeting.md).
 

docs/code-quality/c26407.md

@@ -1,5 +1,6 @@
 ---
 title: C26407
+description: "Reference for Visual Studio C++ Core Guidelines code analysis warning C26407."
 ms.date: 08/18/2020
 ms.topic: "conceptual"
 f1_keywords: ["C26407"]
@@ -12,7 +13,7 @@ To avoid unnecessary use of pointers, we try to detect common patterns of local
 
 ## Remarks
 
-- To reduce the number of warnings, code analysis only detects this pattern for owner pointers. So, it's necessary to mark owners properly first. We can easily extend this to cover raw pointers if we receive [feedback](https://developercommunity.visualstudio.com/spaces/62/index.html) from customers in support of such scenarios.
+- To reduce the number of warnings, code analysis only detects this pattern for owner pointers. So, it's necessary to mark owners properly first. We can easily extend this to cover raw pointers if we receive feedback on the Visual Studio C++ [Developer Community](https://aka.ms/feedback/suggest?space=62) from customers in support of such scenarios.
 
 - The *scoped object* term may be a bit misleading. In general, we suggest you use either a local variable whose lifetime is automatically managed, or a smart object that efficiently manages dynamic resources. Smart objects can of course do heap allocations, but it's not explicit in the code.
 

docs/code-quality/using-the-cpp-core-guidelines-checkers.md

@@ -125,7 +125,7 @@ As new rules are added to the C++ Core Guidelines Checker, the number of warning
 
 - **Enum Rules**: These rules enforce [enum-related checks from the C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#S-enum).<sup>16.3</sup>
 
-- **Experimental Rules** These are experimental C++ Core Check rules that are useful but not ready for everyday use. Try them out and [provide feedback](https://developercommunity.visualstudio.com/content/idea/post.html?space=62).<sup>16.0</sup>
+- **Experimental Rules** These are experimental C++ Core Check rules that are useful but not ready for everyday use. Try them out and [provide feedback](https://aka.ms/feedback/suggest?space=62).<sup>16.0</sup>
 
 - **Function Rules**: Two checks that help with adoption of the **`noexcept`** specifier. They're part of the guidelines for [clear function design and implementation](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#S-functions).<sup>15.5</sup>
 

docs/docfx.json

@@ -57,7 +57,7 @@
       ],
       "feedback_system": "GitHub",
       "feedback_github_repo": "MicrosoftDocs/cpp-docs",
-      "feedback_product_url": "https://developercommunity.visualstudio.com/spaces/62/index.html"
+      "feedback_product_url": "https://aka.ms/feedback/report?space=62"
     },
     "fileMetadata": {
       "ms.tgt_pltfrm": {

docs/error-messages/includes/error-boilerplate.md

@@ -1,11 +1,11 @@
 > [!IMPORTANT]
 > The Visual Studio compilers and build tools can report many kinds of errors and warnings. After an error or warning is found, the build tools may make assumptions about code intent and attempt to continue, so that more issues can be reported at the same time. If the tools make the wrong assumption, later errors or warnings may not apply to your project. When you correct issues in your project, always start with the first error or warning that's reported, and rebuild often. One fix may make many subsequent errors go away.
 
-To get help on a particular diagnostic message in Visual Studio, select it in the **Output** window and press the **F1** key. Visual Studio opens the documentation page for that error, if one exists. You can also use the search tool above to find articles about specific errors or warnings. Or, browse the list of errors and warnings by tool and type in the navigation pane on this page.
+To get help on a particular diagnostic message in Visual Studio, select it in the **Output** window and press the **F1** key. Visual Studio opens the documentation page for that error, if one exists. You can also use the search tool at the top of the page to find articles about specific errors or warnings. Or, browse the list of errors and warnings by tool and type in the table of contents on this page.
 
 > [!NOTE]
-> Not every Visual Studio error or warning is documented. In many cases, the diagnostic message provides all of the information that's available. If you landed on this page when you used **F1** and you think the error or warning message needs additional explanation, let us know. You can use the feedback buttons on this page to raise a documentation issue on [GitHub](https://github.com/MicrosoftDocs/cpp-docs/issues), or a product issue on the [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html) site. You can also send feedback and enter bugs within the IDE. In Visual Studio, go to the menu bar and choose **Help > Send Feedback > Report a Problem**, or submit a suggestion by using **Help > Send Feedback > Send a Suggestion**.
+> Not every Visual Studio error or warning is documented. In many cases, the diagnostic message provides all of the information that's available. If you landed on this page when you used **F1** and you think the error or warning message needs additional explanation, let us know. You can use the feedback buttons on this page to raise a documentation issue on [GitHub](https://github.com/MicrosoftDocs/cpp-docs/issues). If you think the error or warning is wrong, or you've found another problem with the toolset, report a product issue on the [Developer Community](https://aka.ms/feedback/report?space=62) site. You can also send feedback and enter bugs within the IDE. In Visual Studio, go to the menu bar and choose **Help > Send Feedback > Report a Problem**, or submit a suggestion by using **Help > Send Feedback > Send a Suggestion**.
 
-You may find additional assistance for errors and warnings in Microsoft's public forums. Or, search for the error or warning number on the Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/8/index.html) site. You can also search for errors and warnings and ask questions on [Stack Overflow](https://stackoverflow.com/) to find solutions.
+You may find additional assistance for errors and warnings in [Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) forums. Or, search for the error or warning number on the Visual Studio C++ [Developer Community](https://aka.ms/vsfeedback/browsecpp) site. You can also search [Stack Overflow](https://stackoverflow.com/) to find solutions.
 
 For links to additional help and community resources, see [Visual C++ Help and Community](../../overview/visual-cpp-help-and-community.md).

docs/error-messages/tool-errors/linker-tools-error-lnk1104.md

@@ -74,7 +74,7 @@ Make sure you install every version of the library you need for the configuratio
 
 You may see this error if *filename* doesn't exist yet when the linker tries to access it. It can happen when one project depends on another in the solution, but the projects build in the wrong order. To fix this issue, make sure your project references are set in the project that uses the file. Then the missing file gets built before it's required. For more information, see [Adding references in Visual Studio C++ projects](../../build/adding-references-in-visual-cpp-projects.md) and [Managing references in a project](/visualstudio/ide/managing-references-in-a-project).
 
-## Cannot open file 'C:\\Program.obj'
+## Can't open file 'C:\\Program.obj'
 
 If you see the filename *C:\\Program.obj* in the error message, wrap your library paths in double quotes. This error happens when an unwrapped path that begins with *C:\\Program Files* gets passed to the linker. Unwrapped paths may  also cause similar errors. Typically, they show an unexpected .obj file in the root of your drive.
 
@@ -124,6 +124,6 @@ If the *filename* is named LNK*nnn*, it's a filename generated by the linker for
 
 ## Help, my issue isn't listed here!
 
-When none of the issues listed here apply, you can use the feedback tools in Visual Studio for help. In the IDE, go to the menu bar and choose **Help > Send Feedback > Report a Problem**. Or, submit a suggestion by using **Help > Send Feedback > Send a Suggestion**. You can also use the Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html)) website. Use it to search for answers to questions and ask for help. For more information, see [How to report a problem with the Visual C++ toolset or documentation](../../overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md).
+When none of the issues listed here apply, you can use the feedback tools in Visual Studio for help. In the IDE, go to the menu bar and choose **Help > Send Feedback > Report a Problem**. Or, submit a suggestion by using **Help > Send Feedback > Send a Suggestion**. You can also use the [Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) site for questions, and the Visual Studio C++ [Developer Community](https://aka.ms/vsfeedback/browsecpp) website. Use these sites to search for answers to questions and ask for help. For more information, see [How to report a problem with the Visual C++ toolset or documentation](../../overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md).
 
 If you've discovered a new way to fix this issue that we should add to this article, let us know. You can send us feedback by using the button below for **this page**. Use it to create a new issue in our [C++ documentation GitHub repo](https://github.com/MicrosoftDocs/cpp-docs/issues). Thanks!

docs/index.yml

@@ -201,4 +201,4 @@ additionalContent:
             - text: Universal Windows Platform libraries
               url: cppcx/namespaces-reference-c-cx.md
   # footer (optional)
-  footer: "[Blogs](https://devblogs.microsoft.com/cppblog/) - [Twitter](https://twitter.com/visualc) - [Stack Overflow](https://stackoverflow.com/questions/tagged/visual-c++) - [Report an issue](overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md) - [Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html) - Contribute to C++ docs: Read our [contributor guide](/contribute/)."
+  footer: "[Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) - [C++ Team Blog](https://devblogs.microsoft.com/cppblog/) - [Twitter](https://twitter.com/visualc) - [Developer Community](https://aka.ms/vsfeedback/browsecpp) - [Stack Overflow](https://stackoverflow.com/questions/tagged/visual-c++) - [How to report an issue](overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md) - [Suggest a feature](https://aka.ms/feedback/suggest?space=62) - Contribute to C++ docs: Read our [contributor guide](/contribute/)."

docs/linux/deploy-run-and-debug-your-linux-project.md

@@ -86,13 +86,15 @@ There are several ways to interact with and debug your Linux project.
 ## Configure other debugging options (MSBuild projects)
 
 - Command-line arguments can be passed to the executable using the **Program Arguments** item in the project's **Debugging** property page.
-- You can export the `DISPLAY` environment variable by using the **Pre-Launch Command** in the project's**Debugging** property pages. For example: `export DISPLAY=:0.0`
+- You can export the `DISPLAY` environment variable by using the **Pre-Launch Command** in the project's **Debugging** property pages. For example: `export DISPLAY=:0.0`
 
    ![Program Arguments](media/settings_programarguments.png)
 
 - Specific debugger options can be passed to GDB using the **Additional Debugger Commands** entry.  For example, you might want to ignore SIGILL (illegal instruction) signals.  You could use the **handle** command to achieve this by adding the following to the **Additional Debugger Commands** entry as shown above:
 
    `handle SIGILL nostop noprint`
+   
+- You can specify the path to the GDB used by Visual Studio using the **GDB Path** item in the project's **Debugging** property page. This property is available in Visual Studio 2019 version 16.9 and later.
 
 ## Debug with Attach to Process
 

docs/linux/prop-pages/debugging-linux.md

@@ -1,5 +1,6 @@
 ---
 title: "Debugger Properties (Linux C++)| Microsoft Docs"
+description: "Describes the Microsoft Visual Studio Linux C++ debugger properties"
 ms.date: "06/07/2019"
 ms.assetid: 0c1c0fcc-a49b-451c-a5cb-ce9711fac064
 ---
@@ -29,5 +30,6 @@ Linux support is available in Visual Studio 2017 and later.
 | Enable Python Pretty Printing | Enable pretty printing of expression values. Only supported in gdb debugging mode. |
 | Visualization File | Default native visualization file (.natvis) containing visualization directives for SLT types. Other .natvis files that belong to the current solution are loaded automatically. |
 | Additional Sources File Path Map | Additional path equivalences for the debugger to use to map Windows source file names to Linux source file names. The format is "\<windows-path>=\<linux-path>;...". A source file name found under the Windows path is referenced as if it's found in the same relative position under the Linux path. Files found in the local project don't require additional mapping. |
+| GDB Path | **Visual Studio 2019 version 16.9**: Specifies the path to the GDB executable to be used by Visual Studio. |
 
 ::: moniker-end