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

opbld16 · opbld16 · commit 67d05f9ef93d · 2022-10-25T03:04:52.000Z
diff --git a/.openpublishing.redirection.json b/.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",
diff --git a/docs/debugger/includes/remote-debugger-requirements.md b/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.
diff --git a/docs/debugger/remote-debugging-aks-on-linux-with-ssh.md b/docs/debugger/remote-debugging-aks-on-linux-with-ssh.md
diff --git a/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md b/docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.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?
 
diff --git a/docs/debugger/remote-debugging-azure.md b/docs/debugger/remote-debugging-azure.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?
 
diff --git a/docs/debugger/remote-debugging-cpp.md b/docs/debugger/remote-debugging-cpp.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
 
diff --git a/docs/debugger/remote-debugging-csharp.md b/docs/debugger/remote-debugging-csharp.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
 
diff --git a/docs/debugger/remote-debugging-dotnet-core-linux-with-ssh.md b/docs/debugger/remote-debugging-dotnet-core-linux-with-ssh.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)]
diff --git a/docs/debugger/toc.yml b/docs/debugger/toc.yml
@@ -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
diff --git a/docs/porting/port-migrate-and-upgrade-visual-studio-projects.md b/docs/porting/port-migrate-and-upgrade-visual-studio-projects.md
@@ -1,7 +1,7 @@
 ---
 title: Port, migrate, and upgrade projects
 description: A reference for the support of projects created in current and earlier versions of Visual Studio.
-ms.date: 10/18/2022
+ms.date: 10/24/2022
 ms.prod: visual-studio-windows
 ms.technology: vs-ide-general
 ms.topic: conceptual
@@ -116,7 +116,7 @@ Refer to the following articles for further discussion:
 
 ## See also
 
-- [Project migration and upgrade reference for Visual Studio 2017](?view=vs-2017&preserve-view=true)
+- [Project migration and upgrade reference for Visual Studio 2017](/previous-versions/visualstudio/visual-studio-2017/porting/port-migrate-and-upgrade-visual-studio-projects?view=vs-2017&preserve-view=true)
 - [Visual Studio product lifecycle and servicing](/visualstudio/releases/2019/servicing/)
 
 ::: moniker-end
@@ -212,5 +212,6 @@ Refer to the following articles for further discussion:
 ## See also
 
 - [Project migration and upgrade reference for Visual Studio 2019](?view=vs-2019&preserve-view=true)
+- [Support for older versions of Visual Studio](https://devblogs.microsoft.com/visualstudio/support-reminder-for-older-versions-of-visual-studio/)
 
 ::: moniker-end

Original file line number	Diff line number	Diff line change
`@@ -49,4 +49,4 @@ The remote computer must be running one of the following operating systems:`
`49`	`49`
`50`	`50`	`### Network configuration`
`51`	`51`
`52`		`-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.`
	`52`	`+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.`