Merge pull request #10553 from MicrosoftDocs/cxwtool-22583

Merge main into release-17.4

Author: ghogen

.openpublishing.redirection.json

@@ -3020,6 +3020,11 @@
       "redirect_url": "/visualstudio/data-tools/save-data-back-to-the-database",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/debugger/remote-debugging-aks-on-linux-with-ssh.md",
+      "redirect_url": "/visualstudio/debugger/remote-debugging-dotnet-core-linux-with-ssh",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/debugger/using-run-time-checks-without-the-c-run-time-library.md",
       "redirect_url": "/visualstudio/debugger/how-to-use-native-run-time-checks",

docs/azure/vs-azure-tools-storage-resources-server-explorer-browse-manage.md

@@ -151,7 +151,7 @@ The following image shows a queue that contains two messages:
 
 ![Viewing a queue](./media/vs-azure-tools-storage-resources-server-explorer-browse-manage/IC651470.png)
 
-For more information about storage services queues, see [Get started with Azure Queue storage using .NET](/azure/storage/queues/storage-dotnet-how-to-use-queues). For information about the web service for storage services queues, see [Queue Service Concepts](/rest/api/storageservices/Queue-Service-Concepts). For information about how to send messages to a storage services queue by using Visual Studio, see [Sending Messages to a Storage Services Queue](/azure/visual-studio/vs-storage-cloud-services-getting-started-queues).
+For more information about storage services queues, see [Get started with Azure Queue storage using .NET](/azure/storage/queues/storage-dotnet-how-to-use-queues). For information about the web service for storage services queues, see [Queue Service Concepts](/rest/api/storageservices/Queue-Service-Concepts). For information about how to send messages to a storage services queue by using Visual Studio, see [Sending Messages to a Storage Services Queue](/previous-versions/azure/visual-studio/vs-storage-cloud-services-getting-started-queues).
 
 > [!NOTE]
 > Storage services queues are distinct from Azure Service Bus queues. For more information about Service Bus queues, see [Service Bus queues, topics, and subscriptions](/azure/service-bus-messaging/service-bus-queues-topics-subscriptions).

docs/code-quality/code-metrics-cyclomatic-complexity.md

@@ -88,4 +88,4 @@ Watson, A. H., & McCabe, T. J. (1996). Structured Testing: A Testing Methodology
 
 ### SATC
 
-Rosenberg, L., Hammer, T., Shaw, J. (1998). Software Metrics and Reliability (Proceedings of IEEE International Symposium on Software Reliability Engineering). Retrieved May 14, 2011, from Penn State University web site: [http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.104.4041&rep=rep1&type=pdf](http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.104.4041&rep=rep1&type=pdf)
+Rosenberg, L., Hammer, T., Shaw, J. (1998). Software Metrics and Reliability (Proceedings of IEEE International Symposium on Software Reliability Engineering). Retrieved May 14, 2011, from Penn State University web site: [https://citeseerx.ist.psu.edu/pdf/31e3f5732a7af3aecd364b6cc2a85d9495b5c159](https://citeseerx.ist.psu.edu/pdf/31e3f5732a7af3aecd364b6cc2a85d9495b5c159)

docs/debugger/includes/remote-debugger-requirements.md

@@ -49,4 +49,4 @@ The remote computer must be running one of the following operating systems:
 
 ### Network configuration  
 
-The remote computer and the Visual Studio computer must be connected over a network, workgroup, or homegroup, or else connected directly through an Ethernet cable. Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries isn't recommended and may fail or be unacceptably slow.
+The remote computer and the Visual Studio computer must be connected over a network, workgroup, or homegroup, or else connected directly through an Ethernet cable. Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.

docs/debugger/remote-debugging-aks-on-linux-with-ssh.md

@@ -39,7 +39,7 @@ These procedures have been tested on these server configurations:
 The remote debugger is supported on Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low-bandwidth connection, such as dialup Internet, or over the Internet across countries is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low-bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
 
 ## App already running in IIS?
 

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -42,7 +42,7 @@ Visual Studio 2019 or later versions is required to follow the steps shown in th
 
 ### Network requirements
 
-Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries is not recommended and may fail or be unacceptably slow. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
+Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 ## App already running in IIS on the Azure VM?
 

docs/debugger/remote-debugging-azure.md

@@ -35,7 +35,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer and versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 

docs/debugger/remote-debugging-cpp.md

@@ -34,7 +34,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer (not phone) and versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 

docs/debugger/remote-debugging-csharp.md

@@ -2,7 +2,7 @@
 title: "Debug .NET Core on Linux"
 description: Debug .NET Core on Linux using Secure Shell (SSH) by attaching to a process. Prepare your app for debugging. Build and deploy the app. Attach the debugger.
 ms.custom: SEO-VS-2020
-ms.date: "08/24/2021"
+ms.date: "10/24/2022"
 ms.topic: "conceptual"
 helpviewer_keywords:
   - "remote debugging, linux"
@@ -19,6 +19,9 @@ ms.workload:
 
 Starting in Visual Studio 2017, you can attach to .NET Core processes running on a local or remote Linux deployment over Secure Shell (SSH). This article describes how to set up debugging and how to debug. For debugging scenarios using Docker containers, see [Attach to a process running on a Docker container](../debugger/attach-to-process-running-in-docker-container.md) and the [container tools](../containers/edit-and-refresh.md) articles instead. To debug Linux on WSL 2 from Visual Studio (no attach to process), see [Debug .NET Core Apps in WSL 2 with Visual Studio](../debugger/debug-dotnet-core-in-wsl-2.md).
 
+> [!NOTE]
+> For debugging Linux running on Azure Kubernetes Service (AKS), [Bridge to Kubernetes](/visualstudio/bridge/overview-bridge-to-kubernetes.md) is recommended instead of attach to process.
+
 ## Prerequisites
 
 [!INCLUDE [prerequisites-dotnet-linux-ssh](../debugger/includes/prerequisites-dotnet-linux-ssh.md)]

docs/debugger/remote-debugging-dotnet-core-linux-with-ssh.md

@@ -438,8 +438,8 @@
       href: debug-dotnet-core-in-wsl-2.md
     - name: Debug .NET Core on Linux using SSH
       href: remote-debugging-dotnet-core-linux-with-ssh.md
-    - name: Remote debug .NET Core running in AKS on Linux using SSH
-      href: remote-debugging-aks-on-linux-with-ssh.md
+    - name: Debug .NET Core on AKS >>
+      href: /visualstudio/bridge/bridge-to-kubernetes-vs.md
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md
   - name: Application types

docs/debugger/toc.yml

@@ -5,8 +5,8 @@ description: In this quickstart, you use Visual Studio and the Flask framework t
 ms.date: 09/14/2021
 ms.technology: vs-python
 ms.topic: quickstart
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.custom: [vs-acquisition]
 ms.workload:

docs/ide/quickstart-python.md

@@ -86,7 +86,7 @@ The following table lists frequently used properties that are defined in the Vis
 | OptionInfer | Visual Basic | A boolean value that when set to `true`, enables type inference of variables. This property is equivalent to the `/optioninfer` compiler switch. |
 | OptionStrict | Visual Basic | A boolean value that when set to `true`, causes the build task to enforce strict type semantics to restrict implicit type conversions. This property is equivalent to the `/optionstrict` switch of the *vbc.exe* compiler. |
 | OutDir | All | Indicates the final output location for the project or solution. When building a solution, OutDir can be used to gather multiple project outputs in one location. In addition, OutDir is included in AssemblySearchPaths used for resolving references. For example, *bin\Debug*. |
-| OutputPath | All | Specifies the path to the output directory, relative to the project directory, for example, *bin\Debug*. |
+| OutputPath | All | Specifies the path to the output directory, relative to the project directory, for example, *bin\Debug* or *bin\Debug\\$(Platform)* in non-AnyCPU builds.|
 | OutputType | All |  Specifies the file format of the output file. This parameter can have one of the following values:<br /><br /> -   Library. Creates a code library. (Default value.)<br />-   Exe. Creates a console application.<br />-   Module. Creates a module.<br />-   Winexe. Creates a Windows-based program.<br /><br /> For C# and Visual Basic, this property is equivalent to the `/target` switch. The output type can be automatically overridden by inferencing. See [OutputType set to WinExe for WPF and WinForms apps](/dotnet/core/compatibility/sdk/5.0/automatically-infer-winexe-output-type). Disable inferencing by setting `DisableWinExeOutputInference` to `true`. |
 | OverwriteReadOnlyFiles | All | A boolean value that indicates whether you want to enable the build to overwrite read-only files or trigger an error. |
 | PathMap | .NET | Specifies how to map physical paths to source path names output by the compiler. This property is equivalent to the `/pathmap` switch of the compilers. |

docs/msbuild/common-msbuild-project-properties.md

@@ -0,0 +1,44 @@
+---
+title: MSBuild Server | Microsoft Docs
+description: Learn how MSBuild Server supports frequent build scenarios by cacheing build context over multiple builds.
+ms.date: 10/11/2022
+ms.topic: overview
+helpviewer_keywords:
+- MSBuild Server
+author: ghogen
+ms.author: ghogen
+manager: jmartens
+ms.technology: msbuild
+ms.workload:
+- multiple
+---
+# MSBuild Server
+
+MSBuild Server improves the performance of .NET Core builds, which are invoked when you use the `dotnet build` command from the .NET CLI on Windows, Linux, or Mac .NET Core build environments. Instead of starting the build process each time a build is requested, much of the context is cached in a long-running process so it is available to be reused by the next build.  MSBuild Server is not relevant to Visual Studio builds, because Visual Studio acts as a host for MSBuild and already caches all the necessary context.
+
+MSBuild Server is generally not helpful in CI scenarios such as Azure Pipeline builds, because pipelines typically stand up a build environment on demand for each build and then dispose of it when the build is completed.
+
+## Enable MSBuild Server
+
+MSBuild server is not enabled by default; to enable it, set the environment variable `DOTNET_CLI_USE_MSBUILD_SERVER` to `true` or `1`.
+
+Once enabled, for the first time you start a new build process, the build server is launched. When you start the first build, it enables the cache. The cache is persisted after the completion of the first build; the second build therefore proceeds faster since the startup time is significantly reduced due to the cached information. The cache persists after the build is completed, but after an idle time of 15 minutes, it shuts down. Therefore, it is primarily beneficial in repetitive build scenarios where many builds are requested in close succession.
+
+## Shut down or disable MSBuild Server
+
+There are a few different ways to disable the use of MSBuild server. If you just want to shut down the running server, you can issue the command `dotnet build-server shutdown`.
+
+To disable the feature for all builds on a machine, you can set the system environment variable `DOTNET_CLI_USE_MSBUILD_SERVER` to `0` or `false`. You could also set this variable on a per-project basis in a tool like VS Code in `launch.json`.
+
+To disable MSBuild Server for a particular invocation of a command-line build, you can use the option `/nr:false` (or `/node-reuse:false`).
+
+To disable the feature entirely, you can opt out of the change wave that enabled it; `SET MSBuildDisableFeaturesFromVersion="17.4"`. This disabled other features in the same change wave. For more information about change waves, see [MSBuild change waves](change-waves.md).
+
+## Determine the current status of the build server
+
+You can view process status on the machine and look for MSBuild server processes. MSBuild server processes are launched with `dotnet.exe` and show a path to MSBuild.dll and the command option `/nodemode:8`, where `8` indicates MSBuild Server ( `/nodemode:1` indicates the normal MSBuild worker nodes).
+
+## See also
+
+- [dotnet build](/dotnet/core/tools/dotnet-build)
+- [MSBuild](msbuild.md)

docs/msbuild/msbuild-server.md

@@ -113,6 +113,8 @@ items:
         href: item-metadata-in-target-batching.md
     - name: MSBuild transforms
       href: msbuild-transforms.md
+    - name: MSBuild Server
+      href: msbuild-server.md
     - name: Visual Studio integration
       items:
       - name: Visual Studio integration (MSBuild)

docs/msbuild/toc.yml

@@ -3,8 +3,8 @@ title: Configure Python web apps for IIS
 description: How to configure Python web apps to run with Internet Information Services from a Windows virtual machine.
 ms.date: 05/25/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/configure-web-apps-for-iis-windows.md

@@ -3,8 +3,8 @@ title: Data Science and Analytical Applications workload
 description: This Visual Studio workload brings together Python, F#, and their respective runtime distributions including Anaconda. (R is also included in Visual Studio 2017 only.)
 ms.date: 07/28/2021
 ms.topic: overview
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 ms.workload:

docs/python/data-science-and-analytical-applications-workload.md

@@ -3,8 +3,8 @@ title: Mixed-mode debugging for Python
 description: Simultaneously debug C++ and Python in Visual Studio including stepping between environments, viewing values, and evaluating expressions.
 ms.date: 01/26/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/debugging-mixed-mode-c-cpp-python-in-visual-studio.md

@@ -3,8 +3,8 @@ title: Debug Python code on remote Linux computers
 description: Use Visual Studio to debug Python code running on remote Linux computers, including necessary configuration steps, security, and troubleshooting.
 ms.date: 01/17/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/debugging-python-code-on-remote-linux-machines.md

@@ -3,8 +3,8 @@ title: Debug Python code
 description: Visual Studio provides rich debugging for Python code, including setting breakpoints, stepping, inspecting values, looking at exceptions, and debugging in the interactive window.
 ms.date: 01/17/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/debugging-python-in-visual-studio.md

@@ -3,8 +3,8 @@ title: Symbols for mixed-mode Python/C++ debugging
 description: How Visual Studio provides the ability to load symbols for complete mixed-mode C++ and Python debugging.
 ms.date: 01/27/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 ms.workload:

docs/python/debugging-symbols-for-mixed-mode-c-cpp-python.md

@@ -3,8 +3,8 @@ title: Define custom menu commands for Python projects
 description: By editing project and targets files,  you can add custom commands to the Python project context menu in Visual Studio to invoke executable programs, scripts, modules, inline code snippets, and pip.
 ms.date: 01/18/2022
 ms.topic: how-to
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/defining-custom-python-project-commands.md

@@ -3,8 +3,8 @@ title: Edit Python code
 description: For Python, Visual Studio provides rich IntelliSense, code snippets, and navigation features, alongside formatting, linting, and refactoring.
 ms.date: 01/18/2022
 ms.topic: conceptual
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python
 

docs/python/editing-python-code-in-visual-studio.md

@@ -3,8 +3,8 @@ title: Reformat your python code in Visual Studio
 description: Automatically format Python code in Visual Studio, including spacing, statements, wrapping, and comments.
 ms.date: 03/13/2022
 ms.topic: conceptual
-author: ijoosong
-ms.author: joesong
+author: cwebster-99
+ms.author: cowebster
 manager: jmartens
 ms.technology: vs-python