Debugging an ASP.NET Core application hosted on IIS inside an Azure Virtual Machine (VM) is a common enterprise scenario.
It does not support managed code (.NET) debugging or managed/native mixed-mode debugging. It is restricted to native C++ code only.
While actively debugging, go to Debug > Windows > Modules . Find your application's DLL in the list. Check the "Symbol Status" column. If it says "Symbols not loaded," right-click the module and manually navigate to your local .pdb file path. Conclusion visual studio 2022 remote debugger
Change the target launch option from "Local Machine" to .
: Enter the remote machine's name or IP address followed by the port (e.g., RemoteMachine:4026 Select Process Debugging an ASP
within the Remote Debugger window to configure authentication (Windows Authentication is recommended for security). Microsoft Learn 3. Connect from Visual Studio Back on your local development machine: Attach to Process Debug > Attach to Process Ctrl+Alt+P Connection Type : Set this to Remote (Windows) Connection Target
When msvsmon.exe starts, go to to configure your setup. While actively debugging, go to Debug > Windows > Modules
What is the remote target running on? (Windows Server, Linux, Docker, etc.)
If the machines are not on a domain, you must create a local user account on the target machine with the exact same username and password as the account running Visual Studio on your development PC. No Authentication Mode This mode disables all security checks.
Configuration, Architecture, and Best Practices for the Visual Studio 2022 Remote Debugger Date: October 26, 2023 Audience: Software Engineers, DevOps Engineers, and System Administrators