Learn more Skip to main content Microsoft Visual Studio Visual Studio Visual Studio Home Learn About Feedback Problems Suggestions Downloads Support Visual Studio IDE Visual Studio Code Azure DevOps Team Foundation Server Accounts and Subscriptions Subscriber Access More All Microsoft Microsoft 365 Azure Office 365 Dynamics 365 SQL Windows 10 Products Services Windows Server Enterprise Mobility Security Power BI Teams Visual Studio Microsoft Advertising Emerging Technologies AI Internet of Things Azure Cognitive Services Quantum Microsoft HoloLens Mixed Reality Developer IT Docs TechNet Developer Network Windows Dev Center Windows IT Pro Center FastTrack Partner Partner Network Solution Providers Partner Center Cloud Hosting Industries Education Financial services Government Health Manufacturing resources Retail Other Security Licensing AppSource Azure Marketplace Events Research View Sitemap Search Search Microsoft.com Cancel Sign in.To find out exactly whats happening in that environment, you need to set up remote debugging.
Visual Studio Remote Debugging Windows 10 Products ServicesRemote debugging in Visual Studio allows you to step through code, set breakpoints, review objects, inspect the stack, and catch errors on a remote server just as if you were running the code locally. While generally dog slow, this capability is invaluable when mysterious problems crop up in another environment. Microsoft has made the setup of this magical feature pretty simple, but there are a few gotchas that always cause me headaches. Visual Studio Remote Debugging Install The VisualTo get started, you need to install the Visual Studio Remote Tools on the server you want to debug remotely. Once you install the service, youll find a link to the remote tools configuration wizard in the start menu on the server. Running that will allow you to specify the account for the service to run under, or if you prefer, set up the monitoring tool to run as a user account instead of a service. After you complete the wizard you can start the Remote Debugger Monitor by running the program from the servers start menu. Before you do that however, here are two important items to note. If you publish the Release version, the.pdb files which contain all of the debug symbols will not be included and you wont be able to debug remotely. In the Qualifier field, type the IP or the hostname of the server you want to connect to (the port should default to 4018 automatically), then press the Refresh button at the bottom. If youre successful in reaching the server, youll see a list of running processes. Visual Studio Remote Debugging .Exe Process InIf you dont see the w3wp.exe process in the list, be sure youve checked the Show processes from all users box. If you still dont see it, navigate to the application in a web browser to kick off the process, then refresh again. Once you find the w3wp.exe process, highlight it and click the Attach button. Your local client and the server will sync up the symbol files, which can take a minute, and then you should be connected to the remote debugger. Youre now free to set breakpoints in your local code which will be hit from the remote execution. When you do, you should hit your breakpoint just as you would if you had launched the program locally.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |