Launch the application on the target machine. Go to Tools > Options in the Remote Debugger window.
For detailed guidance, refer to Microsoft's documentation on remote debugging ASP.NET Core on a remote IIS computer.
What is running on the target remote machine? (e.g., Windows Server 2022, Linux Docker container)
Once the application is running on the target machine, you can attach the Visual Studio debugger from your development PC. Step 1: Open the Attach to Process Dialog
In the field, enter the remote computer name or IP address and press Enter. visual studio 2022 remote debugger
A common point of failure is symbol loading. The Visual Studio IDE must have access to the exact PDB files matching the binary running on the remote machine.
The remote tools are available for x86, x64, and ARM64 Windows. Installing the Remote Tools
On the remote device or server where your application runs (not on your Visual Studio computer), download the correct version of the remote tools.
Launch the application on the target machine. Go to Tools > Options to configure connectivity: Launch the application on the target machine
when possible, using dedicated service accounts with minimal required privileges.
Ensure the remote debugger is running as an Administrator on the server. Attach to the w3wp.exe process (IIS Worker Process). Debugging WSL/Linux
You must have administrator rights on the target machine. Step-by-Step Guide to Setting Up Remote Debugging 1. Download and Install the Remote Tools
Click to browse available Docker hosts. Add a new connection by entering the server IP address, username, and password, then select the target container instance. What is running on the target remote machine
Deploy your ASP.NET Core application to the remote IIS server using the Debug configuration (not Release).
What or framework are you using? (.NET Core, C++, IIS, etc.)
The remote debugger must match the version of Visual Studio installed on your local machine. Summary Checklist Download Remote Tools for VS 2022 Microsoft Website Run Remote Debugger (msvsmon.exe) Target Machine Configure Firewall Port (Default 4026) Target Machine Connect Debug > Attach to Process Local Machine [5.1]