Merge pull request #8657 from MicrosoftDocs/main638038083245958482sync_temp

Repo sync for protected CLA branch

Author: Court72

docs/containers/edit-and-refresh.md

@@ -7,7 +7,7 @@ manager: jmartens
 ms.assetid: 480e3062-aae7-48ef-9701-e4f9ea041382
 ms.topic: how-to
 ms.workload: multiple
-ms.date: 10/27/2021
+ms.date: 10/07/2022
 ms.technology: vs-container-tools
 ---
 # Debug apps in a local Docker container

docs/containers/troubleshooting-docker-errors.md

@@ -4,7 +4,6 @@ description: Troubleshoot problems you encounter when using Visual Studio to cre
 ms.technology: vs-container-tools
 author: ghogen
 manager: jmartens
-
 ms.assetid: 346f70b9-7b52-4688-a8e8-8f53869618d3
 ms.devlang: dotnet
 ms.topic: troubleshooting
@@ -97,4 +96,10 @@ To resolve this issue, right-click the Docker for Windows icon in the System Tra
 
 ## Other issues
 
-For any other issues, see the [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) repo.
+For any other issues you encounter, see  [Microsoft/DockerTools](https://github.com/microsoft/dockertools/issues) issues.
+
+## See also
+
+- [Visual Studio troubleshooting](/troubleshoot/visualstudio/welcome-visual-studio/)
+- [Container Tools error messages](container-tools-error-messages.md)
+

docs/debugger/toc.yml

@@ -439,7 +439,7 @@
     - name: Debug .NET Core on Linux using SSH
       href: remote-debugging-dotnet-core-linux-with-ssh.md
     - name: Debug .NET Core on AKS >>
-      href: /visualstudio/bridge/bridge-to-kubernetes-vs.md
+      href: /visualstudio/bridge/bridge-to-kubernetes-vs
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md
   - name: Application types

docs/ide/how-to-view-save-and-configure-build-log-files.md

@@ -1,8 +1,8 @@
 ---
-title: 'How to: View, save, and configure build log files | Microsoft Docs'
-description: Learn how you can view, save, and configure build log files. These files provide useful information for tasks like troubleshooting a build failure.
+title: 'How to: View, save, and configure build log files'
+description: Learn how you can view, save, and configure build log files. These files provide information such as the command lines used for the compiler and other tools, which can help you troubleshoot build failures.
 ms.custom: SEO-VS-2020
-ms.date: 09/12/2022
+ms.date: 11/11/2022
 ms.technology: vs-ide-compile
 ms.topic: how-to
 ms.assetid: 75d38b76-26d6-4f43-bbe7-cbacd7cc81e7
@@ -16,11 +16,11 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-After you build a project in the Visual Studio IDE, you can view information about that build in the **Output** window. By using this information, you can, for example, troubleshoot a build failure.
+After you build a project in the Visual Studio IDE, you can view information about that build in the **Output** window. By using this information, you can troubleshoot a build failure, view the exact command lines used for all the build tools, or get full diagnostic information about the entire build process.
 
 - For C++ projects, you can also view the same information in a log file that's created and saved when you build a project.
 
-- For managed code projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a log file.
+- For .NET projects, you can click in the build output window and press **Ctrl**+**S**. Visual Studio prompts you for a location to save the information from the **Output** window into a log file.
 
 You can also use the IDE to specify what kinds of information you want to view about each build.
 
@@ -48,20 +48,25 @@ You can also generate logs by running MSBuild directly from the command line, us
 
 2. On the **Projects and Solutions** page, choose the **Build and Run** page.
 
-3. In the **MSBuild project build output verbosity** list, choose one of the following values, and then choose the **OK** button.
+3. In the **MSBuild project build output verbosity** list, choose one of the values, and then choose the **OK** button.
 
-    |Verbosity level|Description|
-    | - |-----------------|
-    |**Quiet**|Displays a summary of the build only.|
-    |**Minimal**|Displays a summary of the build and errors, warnings, and messages that are categorized as highly important.|
-    |**Normal**|Displays a summary of the build; errors, warnings, and messages that are categorized as highly important; and the main steps of the build. You'll use this level of detail most frequently.|
-    |**Detailed**|Displays a summary of the build; errors, warnings, and messages that are categorized as highly important; all of the steps of the build; and messages that are categorized as of normal importance.|
-    |**Diagnostic**|Displays all data that's available for the build. You can use this level of detail to help debug issues with custom build scripts and other build issues.|
+The following table shows how the log verbosity (column values) affects which types of message (row values) are logged.
 
-     For more information, see [Options dialog box,  Projects and Solutions, Build and Run](../ide/reference/options-dialog-box-projects-and-solutions-build-and-run.md) and <xref:Microsoft.Build.Framework.LoggerVerbosity>.
+| Message type / Verbosity              | Quiet | Minimal | Normal | Detailed | Diagnostic |
+|---------------------------------------|:-----:|:-------:|:------:|:--------:|:----------:|
+| Errors                                |   ✅   |    ✅    |    ✅   |     ✅    |      ✅     |
+| Warnings                              |   ✅   |    ✅    |    ✅   |     ✅    |      ✅     |
+| High-importance Messages              |       |    ✅    |    ✅   |     ✅    |      ✅     |
+| Normal-importance  Messages           |       |         |    ✅   |     ✅    |      ✅     |
+| Low-importance  Messages              |       |         |        |     ✅    |      ✅     |
+| Additional MSBuild-engine information |       |         |        |          |      ✅     |
 
-    > [!IMPORTANT]
-    > You must rebuild the project for your changes to take effect in the **Output** window (all projects) and the *\<ProjectName>.txt* file (C++ projects only).
+If you want to see the command lines used for the compiler and other tools, choose at least the **Detailed** verbosity level.
+
+For more information, see [Options dialog box,  Projects and Solutions, Build and Run](../ide/reference/options-dialog-box-projects-and-solutions-build-and-run.md) and <xref:Microsoft.Build.Framework.LoggerVerbosity>.
+
+> [!IMPORTANT]
+> You must rebuild the project for your changes to take effect in the **Output** window (all projects) and the *\<ProjectName>.txt* file (C++ projects only).
 
 ## Use binary logs to make it easier to browse large log files
 
@@ -75,3 +80,4 @@ Binary logs are an optional feature for .NET projects that lets you have a riche
 
 - [Build and clean projects and solutions in Visual Studio](../ide/building-and-cleaning-projects-and-solutions-in-visual-studio.md)
 - [Compile and build](../ide/compiling-and-building-in-visual-studio.md)
+- [Obtaining build logs with MSBuild](../msbuild/obtaining-build-logs-with-msbuild.md)