Add instructions and links to clarify remote debugging scenarios for C# and C++ (#13524)

Mikejo5000 · Court72 · web-flow · commit 35a62e600689 · 2025-01-24T16:59:35.000-07:00
* Add instructions and links related to remote debugging C# and C++ from application startup

* edits

* Update Hot Reload settings

* edits

* Fix blocking issue in PR review - Acrolinx

---------

Co-authored-by: Courtney Wales &lt;62625502+Court72@users.noreply.github.com&gt;
diff --git a/docs/debugger/how-to-enable-debugging-for-aspnet-applications.md b/docs/debugger/how-to-enable-debugging-for-aspnet-applications.md
@@ -22,7 +22,7 @@ ms.subservice: debug-diagnostics
 You can debug ASP.NET and ASP.NET Core apps in Visual Studio. The process differs between ASP.NET and ASP.NET Core, and whether you run it on IIS Express or a local IIS server.
 
 >[!NOTE]
->The following steps and settings apply only to debugging apps on a local server. Debugging apps on a remote IIS server uses **Attach to Process**, and ignores these settings. For more information and instructions for remote debugging ASP.NET apps on IIS, see [Remote debug ASP.NET on an IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md) or [Remote debug ASP.NET Core on a remote IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md).
+>The following steps and settings apply only to debugging apps on a local server. Debugging apps on a remote IIS server uses **Attach to Process**, and ignores these settings. For more information and instructions for remote debugging ASP.NET and ASP.NET Core, see [Remote debug ASP.NET Core on a remote IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md), and [Remote debug Azure App Service](../debugger/remote-debugging-azure-app-service.md).
 
 ::: moniker range=">=vs-2022"
 The built-in Kestrel and IIS Express servers are included with Visual Studio. Kestrel is the default debug server for ASP.NET Core projects, and is preconfigured. IIS Express is the default debug server for ASP.NET.
@@ -43,7 +43,7 @@ You can also debug an ASP.NET or ASP.NET Core app on a local IIS server (version
 
 - Run Visual Studio as an administrator.
 - Install and correctly configure IIS with the appropriate version(s) of ASP.NET and/or ASP.NET Core. For more information on using IIS with ASP.NET Core, see [Host ASP.NET Core on Windows with IIS](/aspnet/core/host-and-deploy/iis/index). For ASP.NET, see [Install IIS and ASP.NET Modules](/iis/application-frameworks/scenario-build-an-aspnet-website-on-iis/configuring-step-1-install-iis-and-asp-net-modules).
-- Make sure the app runs on IIS without errors.
+- Make sure the app runs on IIS and opens in the browser.
 
 ::: moniker range=">=vs-2022"
 ## Debug ASP.NET Core apps
diff --git a/docs/debugger/includes/remote-debugger-requirements.md b/docs/debugger/includes/remote-debugger-requirements.md
@@ -31,9 +31,6 @@ The remote computer must be running one of the following operating systems:
 - Windows Server 2012 or Windows Server 2012 R2  
   
 - Windows Server 2008 Service Pack 2, Windows Server 2008 R2 Service Pack 1
-
-> [!NOTE]
-> Windows Phone requires a USB connection to debug (it does not require the remote tools).
   
 ### Supported Hardware Configurations  
   
diff --git a/docs/debugger/remote-debugging.md b/docs/debugger/remote-debugging.md
@@ -26,13 +26,13 @@ For in-depth instructions on remote debugging, see these topics.
 
 |Scenario|Link|
 |-|-|
-|Azure App Service|[Remote debug ASP.NET Core on Azure](../debugger/remote-debugging-azure-app-service.md) or, for Visual Studio Enterprise, the [Snapshot Debugger](../debugger/debug-live-azure-applications.md)|
-|Azure VM|[Remote debug ASP.NET on an Azure VM](../debugger/remote-debugging-azure.md)|
-|ASP.NET|[Remote debug ASP.NET Core](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md) or [Remote Debug ASP.NET](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md)|
 |C# or Visual Basic|[Remote debug a C# or Visual Basic project](../debugger/remote-debugging-csharp.md)|
 |C++|[Remote debug a C++ project](../debugger/remote-debugging-cpp.md)|
-|Docker|[Attach to a process running in a Docker container](../debugger/attach-to-process-running-in-docker-container.md)|
+|Azure App Service|[Remote debug ASP.NET Core on Azure](../debugger/remote-debugging-azure-app-service.md) or, for Visual Studio Enterprise, the [Snapshot Debugger](../debugger/debug-live-azure-applications.md)|
+|ASP.NET|[Remote debug ASP.NET Core](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md) or [Remote Debug ASP.NET](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md)|
+|Azure VM|[Remote debug ASP.NET on an Azure VM](../debugger/remote-debugging-azure.md)|
 |Linux|[Debug .NET Core on Linux using SSH by attaching to a process](../debugger/remote-debugging-dotnet-core-linux-with-ssh.md)|
+|Docker|[Attach to a process running in a Docker container](../debugger/attach-to-process-running-in-docker-container.md)|
 |Universal Windows Apps (UWP)|[Run UWP apps on a remote machine](../debugger/run-windows-store-apps-on-a-remote-machine.md) or [Debug an installed app package](../debugger/debug-installed-app-package.md)|
 
 If you just want to download and install the remote debugger and don't need any additional instructions for your scenario, follow the steps in this article.
@@ -88,13 +88,21 @@ You can change some aspects of the configuration of the remote debugger after yo
 
      Alternatively, you can start the remote debugger from the command line with the **/allow \<username>** parameter: **msvsmon /allow \<username@computer>**.
 
-- If you need to change the Authentication mode or the port number, or specify a timeout value for the remote tools: choose **Tools > Options**.
+- If you need to change the Authentication mode or the port number, or specify a time-out value for the remote tools: choose **Tools > Options**.
 
      For a listing of the port numbers used by default, see [Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md).
 
      > [!WARNING]
      > You can choose to run the remote tools in No Authentication mode, but this mode is strongly discouraged. There's no network security when you run in this mode. Choose the No Authentication mode only if you're sure that the network isn't at risk from malicious or hostile traffic.
 
+## Configure Visual Studio for remote debugging
+
+For detailed instructions to connect to the app from Visual Studio, use the links related to your specific scenario at the beginning of this article.
+
+Some scenarios require the use of Attach to Process to connect to a remote app that is already started. However, for .NET Core, .NET 5+, .NET Framework, and C++ apps, you can start the remote app from Visual Studio by configuring project properties and starting the debugger. For more information, see [Remote debug a C# or Visual Basic project](../debugger/remote-debugging-csharp.md) or [Remote debug a C++ project](../debugger/remote-debugging-cpp.md).
+
+You can also remote debug an executable that is not part of a Visual Studio project, although the supported debugging features depend on configuration such as the availability of symbols. For more information, see [Debug an app that isn't part of a Visual Studio solution](../debugger/how-to-debug-an-executable-not-part-of-a-visual-studio-solution.md).
+
 ## <a name="bkmk_configureService"></a> (Optional) Configure the remote debugger as a service
 
 For debugging in ASP.NET and other server environments, you must either run the remote debugger as an Administrator or, if you want it always running,  run the remote debugger as a service.
