Merge pull request #6408 from Mikejo5000/mikejo-br17

Remote debugging error ref work

Author: PRMerger7

docs/debugger/remote-debugging-azure.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debug ASP.NET Core on IIS and Azure | Microsoft Docs"
 ms.custom: "remotedebugging"
-ms.date: "05/21/2018"
+ms.date: "04/14/2020"
 ms.topic: "conceptual"
 ms.assetid: a6c04b53-d1b9-4552-a8fd-3ed6f4902ce6
 author: "mikejo5000"
@@ -67,19 +67,25 @@ Debugging between two computers connected through a proxy is not supported. Debu
 
 From Visual Studio, you can quickly publish and debug your app to a fully provisioned instance of IIS. However, the configuration of IIS is preset and you cannot customize it. For more detailed instructions, see [Deploy an ASP.NET Core web app to Azure using Visual Studio](/aspnet/core/tutorials/publish-to-azure-webapp-using-vs). (If you need the ability to customize IIS, try debugging on an [Azure VM](#remote_debug_azure_vm).)
 
-#### To deploy the app and remote debug using Server Explorer
+#### To deploy the app and remote debug using Cloud Explorer
 
 1. In Visual Studio, right-click the project node and choose **Publish**.
 
     If you have previously configured any publishing profiles, the **Publish** pane appears. Click **New profile**.
 
-1. Choose **Azure App Service** from the **Publish** dialog box, select **Create New**, and follow the prompts to publish.
+1. Choose **Azure App Service** from the **Publish** dialog box, select **Create New**, and follow the prompts to create a profile.
 
     For detailed instructions, see [Deploy an ASP.NET Core web app to Azure using Visual Studio](/aspnet/core/tutorials/publish-to-azure-webapp-using-vs).
 
     ![Publish to Azure App Service](../debugger/media/remotedbg_azure_app_service_profile.png)
 
-1. Open **Server Explorer** (**View** > **Server Explorer**), right-click on the App Service instance and choose **Attach Debugger**.
+1. In the Publish window, choose **Edit Configuration** and switch to a Debug configuration, and then choose **Publish**.
+
+   A Debug configuration is required to debug the app.
+
+1. Open **Cloud Explorer** (**View** > **Cloud Explorer**), right-click on the App Service instance and choose **Attach Debugger**.
+
+   If Cloud Explorer is not available, open Server Explorer instead. Then, right-click on the App Service instance in Server Explorer and choose **Attach Debugger**.
 
 1. In the running ASP.NET application, click the link to the **About** page.
 

docs/debugger/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md

@@ -1,6 +1,6 @@
 ---
 title: "Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor | Microsoft Docs"
-ms.date: "08/24/2017"
+ms.date: "04/14/2020"
 ms.topic: "reference"
 f1_keywords:
   - "vs.debug.error.remote_debug"
@@ -61,6 +61,18 @@ In the **Attach to Process** dialog box or in the project properties, make sure
 
 If these values are correct and the message mentions **Windows Authentication** mode, check that the remote debugger is in the correct authentication mode (**Tools > Options**).
 
+## <a name="connection_terminated"></a> The connection with the remote endpoint was terminated
+
+If you are debugging an Azure App Service app, try using the [Attach Debugger](../debugger/remote-debugging-azure.md#remote_debug_azure_app_service) command from Cloud Explorer or Server Explorer instead of **Attach to Process**.
+
+If you are using **Attach to Process** to debug:
+
+1. In the **Attach to Process** dialog box or in the project properties, make sure that the remote computer name and the port number matches the name and port number shown in the remote debugger window. If incorrect, fix and try again.
+
+2. Check the application log on the server (Event Viewer on Windows) for more detailed information to help resolve the issue.
+
+3. Otherwise, try restarting Visual Studio with Administrator privileges, and then try again.
+
 ## <a name="invalid_access"></a> Invalid access to memory location
 
 An internal error occurred. Restart Visual Studio and try again.