Your ASP. NET project source code, while ensuring that the remote server is used by the source of the compilation generated (Debug, release version is OK)
Locate the corresponding debug version in the Microsoft Visual studio/visual Studio tools/remote Debugger folder directory to the remote server
Http://jingyan.baidu.com/article/59a015e3a75708f794886533.html
In fact, I want to monitor the process recycle mechanism of IIS on the server, see if I write the cache regular update is not available. Local XP is not able to install IIS6.0, there is no way to use remote debugging.
Debug the existing code.
The steps are simple:
1. Start the remote debugging component
1) Install the Debug component: Only the remote debugger remote debugging component of Visual Studio can be installed on the server , and the specific installation method is described in detail on MSDN.
2) Run the Debug component: After the installation is complete, under the Start menu, under Visual Studio Tools, run remote Debuger. Or find the file C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\Remote Debugger\x86\msvsmon.exe.
2. Commissioning
1) Change the virtual path. Copy the code of the solution you want to debug and share it with the remote server. On IIS, set the virtual path for the Web site to be debugged, pointing to the presentation layer under the solution.
2) Open the solution code on the remote server locally.
3) attach to the process. After running, you can attach the process to the remote server under the local Visual Studio development platform. Debug > Attach to process. In the Attach to Process window, select the qualifier as the remote server name, and, of course, ensure that the user has administrator privileges on the remote server.
This will be OK, set breakpoints to debug it.
WebService debugging is also the same.