![]() The User code column indicates whether the module you're trying to debug is classified as My Code.The Symbol Status column indicates whether symbols loaded correctly for the module.Use the Modules window to find out the symbol loading status for your module, and which modules the debugger is treating as user code, or My Code. (You may be choosing a debug build when you run the app in Visual Studio, but that doesn't mean you installed a debug build on the server.) You can attach to the remote application, but you can't hit breakpoints (or debugging symbols won't load)įor this issue, you may see a message No symbols are loaded. The Publish tool and some other publishing options have a separate debug configuration setting that you need to set. A release build is deployed to the server instead of a debug build For current links to download the remote debugger, see Remote Debugger. ![]() Otherwise, here are the most common issues and solutions: Incorrect version of the remote debugger installedįor scenarios where you manually install the remote debugger on a remote machine, make sure the installed version matches your version of Visual Studio. Next, verify that the app is running correctly on the server before trying to debug it. The message may include a link with more information. To troubleshoot remote debugging issues, the first step is to check for error messages and investigate. This article introduces troubleshooting steps and solutions of some common issues with remote debugging.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |