If your app is running in IIS and you just want to download the remote debugger and start debugging, go to Download and Install the remote tools on Windows Server.

These steps are included to make sure that the server has required components installed, that the app can run correctly, and that you are ready to remote debug. This article includes steps on setting up a basic configuration of IIS on Windows server and deploying the app from Visual Studio. For a complete list of requirements, see Requirements. 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. These procedures have been tested on these server configurations:ĭebugging between two computers connected through a proxy is not supported. Visual Studio 2019 or a later version is required to follow the steps shown in this article. For Azure App Service, see Remote debug ASP.NET Core on Azure or, for Visual Studio Enterprise, use the Snapshot Debugger (.NET 4.6.1 required). You can also deploy and debug on IIS using Azure.

To remote debug ASP.NET 4.8, see Remote Debug ASP.NET on an IIS Computer. This guide explains how to set up and configure a Visual Studio ASP.NET Core, deploy it to IIS, and attach the remote debugger from Visual Studio. To debug an ASP.NET Core application that has been deployed to IIS, install and run the remote tools on the computer where you deployed your app, and then attach to your running app from Visual Studio. Applies to: Visual Studio Visual Studio for Mac Visual Studio Code

Visual studio code debug with iis