Merge branch 'main' into pythonupdates

Author: cwebster-99

.github/workflows/stale-issues.yml

@@ -29,6 +29,6 @@ jobs:
           exempt-issue-labels: 'exempt'
           remove-stale-when-updated: true
           days-before-close: 14
-          days-before-issue-stale: 180
+          days-before-issue-stale: 90
           days-before-pr-stale: -1
           operations-per-run: 500

.openpublishing.redirection.json

@@ -1,5 +1,10 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/msbuild/updating-an-existing-application.md",
+      "redirect_url": "/visualstudio/msbuild/find-and-use-msbuild-versions",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/python/managing-python-on-azure-app-service.md",
       "redirect_url": "/azure/app-service/quickstart-python",
@@ -3020,6 +3025,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",
@@ -3910,6 +3920,11 @@
       "redirect_url": "/visualstudio/xaml-tools/creating-a-ui-by-using-xaml-designer-in-visual-studio",
       "redirect_document_id": true
     },
+    {
+      "source_path": "docs/designers/getting-started-with-wpf.md",
+      "redirect_url": "/visualstudio/get-started/csharp/tutorial-wpf",
+      "redirect_document_id": true
+    },
     {
       "source_path": "docs/debugger/debug-xaml-in-blend.md",
       "redirect_url": "/visualstudio/xaml-tools/debug-xaml-in-blend",

docs/azure/azure-cosmosdb-add-connected-service.md

@@ -55,7 +55,7 @@ The connected service functionality adds all the needed references and connectio
 
     If you need to create a database, go to the next step. Otherwise, skip to step 7.
 
-    ![Add existing Cosmos DB to project](./media/azure-cosmosdb-add-connected-service/created-cosmosdb.png)
+    ![Add existing Azure Cosmos DB to project](./media/azure-cosmosdb-add-connected-service/created-cosmosdb.png)
 
 1. To create an Azure Cosmos DB:
 

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/code-quality/roslyn-analyzers-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Code analysis using Roslyn analyzers
+title: Code analysis using Roslyn analyzers 
 ms.date: 01/15/2022
 description: Become familiar with source code analysis in Visual Studio. Learn about code fixes and the different types of analyzers and severity levels.
 ms.custom: SEO-VS-2020, devdivchpfy22

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/data-tools/index.yml

@@ -70,9 +70,9 @@ landingContent:
         links:
           - text: Azure SQL database
             url: /azure/sql-database/sql-database-connect-query-dotnet-visual-studio
-          - text: Cosmos DB - .NET console app
+          - text: Azure Cosmos DB - .NET console app
             url: /azure/cosmos-db/sql-api-get-started
-          - text: Cosmos DB - .NET web app
+          - text: Azure Cosmos DB - .NET web app
             url: /azure/cosmos-db/sql-api-dotnet-application
           - text: Azure Data Lake Analytics
             url: /azure/data-lake-analytics/data-lake-analytics-data-lake-tools-get-started

docs/data-tools/troubleshooting-service-references.md

@@ -28,6 +28,13 @@ This topic lists solutions to common issues that may occur when you are working
 
 If you want to update or remove a service reference, see the article "[Add, update, or remove a WCF data service reference](how-to-add-update-or-remove-a-wcf-data-service-reference.md)".
 
+## Error when no service address is provided
+
+When you press the **Go** button with no address, you may see an error message that says "Please enter the address for a service." To resolve this, you need to identify a service's address and enter it.
+
+- If it's a service in your solution, you can use the **Discover** button to find and select it, and then try the **Go** button again.
+- If it's a service hosted somewhere on the internet, add it by following the instructions at [Add a WCF service reference](how-to-add-update-or-remove-a-wcf-data-service-reference.md#add-a-wcf-service-reference).
+
 ## Error returning data from a service
 
 When you return a `DataSet` or `DataTable` from a service, you may receive a "The maximum size quota for incoming messages has been exceeded" exception. By default, the `MaxReceivedMessageSize` property for some bindings is set to a relatively small value to limit exposure to denial-of-service attacks. You can increase this value to prevent the exception. For more information, see <xref:System.ServiceModel.HttpBindingBase.MaxReceivedMessageSize%2A>.

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) 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
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md
   - name: Application types