Add aka.ms links for DevCom2

Colin Robertson · Colin Robertson · commit e160e60f8b13 · 2020-11-05T16:33:28.000-08:00
diff --git a/docs/code-quality/c26407.md b/docs/code-quality/c26407.md
@@ -12,7 +12,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.
 
diff --git a/docs/code-quality/using-the-cpp-core-guidelines-checkers.md b/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>
 
diff --git a/docs/docfx.json b/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": {
diff --git a/docs/error-messages/includes/error-boilerplate.md b/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 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://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).
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1104.md b/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 [Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) site for questions, and the Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html)) 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).
+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!
diff --git a/docs/index.yml b/docs/index.yml
@@ -201,4 +201,4 @@ additionalContent:
             - text: Universal Windows Platform libraries
               url: cppcx/namespaces-reference-c-cx.md
   # footer (optional)
-  footer: "[Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) - [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) - [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://aka.ms/feedback/report?space=62) - Contribute to C++ docs: Read our [contributor guide](/contribute/)."
diff --git a/docs/overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md b/docs/overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md
@@ -356,7 +356,7 @@ Create your repro as a minimal IDE project, then package it by compressing the e
 
 ## Ways to send your report
 
-You have a couple of good ways to get your report to us. You can use Visual Studio's built-in [Report a Problem Tool](/visualstudio/ide/how-to-report-a-problem-with-visual-studio-2017), or the [Visual Studio Developer Community](https://developercommunity.visualstudio.com/) pages. There's also a **Product feedback** button at the bottom of this page. The choice depends on whether you want to use the built-in tools in the IDE to capture screenshots and organize your report. If you prefer not to, you can use the Developer Community website directly.
+You have a couple of good ways to get your report to us. You can use Visual Studio's built-in [Report a Problem Tool](/visualstudio/ide/how-to-report-a-problem-with-visual-studio), or the [Visual Studio Developer Community]( https://aka.ms/feedback/report?space=62) page. There's also a **Product feedback** button at the bottom of this page. The choice depends on whether you want to use the built-in tools in the IDE to capture screenshots and organize your report. If you prefer not to, you can use the Developer Community website directly.
 
 > [!NOTE]
 > Regardless of how you submit your report, Microsoft respects your privacy. Microsoft is committed to compliance with all data privacy laws and regulations. For information about how we treat the data that you send us, see the [Microsoft Privacy Statement](https://privacy.microsoft.com/privacystatement).
@@ -371,14 +371,14 @@ When you choose to report a problem, first search the Developer Community for si
 
 ### Use the Visual Studio Developer Community pages
 
-The Visual Studio Developer Community pages are another convenient way to report problems and find solutions for Visual Studio and the C++ compiler, tools, and libraries. There are specific Developer Community pages for [Visual Studio](https://developercommunity.visualstudio.com/spaces/8/index.html), [Visual Studio for Mac](https://developercommunity.visualstudio.com/spaces/41/index.html), [.NET](https://developercommunity.visualstudio.com/spaces/61/index.html), [C++](https://developercommunity.visualstudio.com/spaces/62/index.html), [Azure DevOps Services](https://developercommunity.visualstudio.com/spaces/21/index.html), and [TFS](https://developercommunity.visualstudio.com/spaces/22/index.html).
+The Visual Studio Developer Community pages are another convenient way to report problems and find solutions for Visual Studio and the C++ compiler, tools, and libraries. There are specific Developer Community pages for [Visual Studio](https://aka.ms/feedback/report?space=8), [Visual Studio for Mac](https://aka.ms/feedback/report?space=41), [.NET](https://aka.ms/feedback/report?space=61), [C++](https://aka.ms/feedback/report?space=62), [Azure DevOps](https://aka.ms/feedback/report?space=21), and [Azure DevOps Server](https://aka.ms/feedback/report?space=22).
 
 Beneath the community tabs, near the top of each page, is a search box. You can use it to find posts that report problems similar to yours. You may find a solution or other useful information related to your problem is already available. If someone has reported the same problem before, then upvote and comment on that report, rather than create a new problem report. To comment, vote, or report a new problem, you may be asked to sign in to your Visual Studio account. The first time you sign in, you'll have to agree to give the Developer Community app access to your profile.
 
-For issues with the C++ compiler, linker, and other tools and libraries, use the [C++ Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html) page. If you search for your problem, and it hasn't been reported before, choose the **Report a problem** button next to the search box. You can include your repro code and command line, screenshots, links to related discussions, and any other information you think is relevant and useful.
+For issues with the C++ compiler, linker, and other tools and libraries, first search the [C++ Developer Community](https://aka.ms/vsfeedback/browsecpp) page. If you search for your problem, and it hasn't been reported before, choose the **Report a problem** button next to the search box. You can include your repro code and command line, screenshots, links to related discussions, and any other information you think is relevant and useful.
 
 > [!TIP]
-> For other kinds of problems you might find in Visual Studio that are unrelated to the C++ toolset (For example, UI issues, broken IDE functionality, or general crashes), use the **Report a Problem** tool in the IDE. This is the best choice, due to its screenshot capabilities and its ability to record UI actions that lead to the problem you've found. These kinds of errors can also be looked up on the [Developer Community](https://developercommunity.visualstudio.com/) site. For more information, see [How to report a problem with Visual Studio](/visualstudio/ide/how-to-report-a-problem-with-visual-studio-2017).
+> For other kinds of problems you might find in Visual Studio that are unrelated to the C++ toolset (For example, UI issues, broken IDE functionality, or general crashes), use the **Report a Problem** tool in the IDE. This is the best choice, due to its screenshot capabilities and its ability to record UI actions that lead to the problem you've found. These kinds of errors can also be looked up on the Visual Studio [Developer Community](https://aka.ms/feedback/report?space=8) site. For more information, see [How to report a problem with Visual Studio](/visualstudio/ide/how-to-report-a-problem-with-visual-studio).
 
 ### Reports and privacy
 
diff --git a/docs/overview/visual-cpp-help-and-community.md b/docs/overview/visual-cpp-help-and-community.md
@@ -1,6 +1,7 @@
 ---
 title: "Visual C++ Help and Community"
-ms.date: 08/03/2020
+description: "This article lists various additional resources for help and information on Visual Studio and the Microsoft C/C++ compiler and tools."
+ms.date: 11/05/2020
 ms.technology: "cpp-ide"
 ms.assetid: 6bc23c18-fcd9-47bc-bff2-17537700be4a
 ---
@@ -10,30 +11,30 @@ Here's where to get help and information about how to write C++ code and use the
 
 ## Samples
 
-|Title|Description|
-|-----------|-----------------|
-|[Developer Code Samples](/samples)|Contains downloadable sample code from Microsoft and community contributors.|
+- [Developer Code Samples](/samples): Contains downloadable sample code from Microsoft and community contributors.
 
 ## Product Documentation
 
-|Title|Description|
-|-----------|-----------------|
-|[C++ in Visual Studio](visual-cpp-in-visual-studio.md)|Contains reference and conceptual documentation about Visual C++.|
-|[Windows Developer Center](https://developer.microsoft.com/windows/)|Contains information about how to use C++ and other languages to develop apps for Windows 10. Part of the Windows Developer Center; the C++ content is under the Docs > Language Reference node.|
+- [C++ in Visual Studio](visual-cpp-in-visual-studio.md): Contains reference and conceptual documentation about Visual C++.
+
+- [Windows Developer Center](https://developer.microsoft.com/windows/): Contains information about how to use C++ and other languages to develop apps for Windows 10.
 
 ### Online and Offline Documentation
 
 You can view Microsoft developer content online. This content is updated regularly.
 
 You can also download and view the content locally in the offline Help Viewer. The offline documentation is organized by books of related content, which are also updated periodically. You can download the books you are interested in as they become available. For more information, see [Microsoft Help Viewer](/visualstudio/ide/microsoft-help-viewer).
 
-Many sections of the documentation are also available in PDF form. These sections have a **Download PDF** link on included pages on docs.microsoft.com.
+Many sections of the documentation are also available in PDF form. These sections have a **Download PDF** link below the table of contents on docs.microsoft.com.
 
 ## Related Articles
 
-|Title|Description|
-|-----------|-----------------|
-|[C++ Team Blog](https://devblogs.microsoft.com/cppblog/)|Contains posts on various subjects by the experts on Microsoft's C++ product team.|
-|[Channel 9](https://channel9.msdn.com/)|Contains video interviews and lectures. Use the search box on the Channel 9 home page to find C++ content.|
-|[Visual Studio](https://visualstudio.microsoft.com/)|Contains articles and news about Visual Studio and related development tools.|
-|[Microsoft Docs Q&A](/answers/topics/c%2B%2B.html) and Visual Studio C++ [Developer Community](https://developercommunity.visualstudio.com/spaces/62/index.html)|Official Microsoft forums where you can post questions about C++ and get answers from Microsoft and from experts in the community.|
+- [C++ Team Blog](https://devblogs.microsoft.com/cppblog/): Contains posts on various subjects by the experts on Microsoft's C++ product team.
+
+- [Channel 9](https://channel9.msdn.com/): Contains video interviews and lectures. Use the search box on the Channel 9 home page to find C++ content.
+
+- [Visual Studio website](https://visualstudio.microsoft.com/): Contains articles and news about Visual Studio and related development tools. This site also hosts Visual Studio downloads and redistributable files. |
+
+- [Microsoft Docs Q&A](/answers/topics/c%2B%2B.html): Official Microsoft forums where you can post questions about C++ and Visual Studio and get answers from Microsoft and from experts in the community.
+
+- [Visual Studio C++ Developer Community](https://aka.ms/vsfeedback/browsecpp): Forums for reporting problems in the C++ compiler and tools or the IDE, or for making product suggestions. You can vote for your favorite ideas or bug reports, or add a new one. This site is monitored by the development team.
diff --git a/docs/overview/visual-cpp-in-visual-studio.md b/docs/overview/visual-cpp-in-visual-studio.md
diff --git a/docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md b/docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md
diff --git a/docs/porting/upgrading-projects-from-earlier-versions-of-visual-cpp.md b/docs/porting/upgrading-projects-from-earlier-versions-of-visual-cpp.md
