0
On Server side:
the most important is that the compiled version should be in "Debug" mode because the released version doesnt have the debugging information.
you have to install the "Visual Studio 2008 Service Pack 1 Remote Debugger".
you can download "Visual Studio 2008 Service Pack 1 Remote Debugger" from here
once you have installed it, run the service with "Local Account" authentication. and then run the debugger "rdbgwiz.exe" and allow the users on the domian to connect to the debugger remotly.
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\rdbgwiz.exe
afterward run "MSVSSMON.EXE" as Administrator. otherwise you can not debug "w3wp.exe"
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86\msvsmon.exe
On Developer side:
To attach to a running ASP.NET application, you have to know the name of the ASP.NET process:
If you are running IIS 6.0 or IIS 7.0, the name is w3wp.exe.
If you are running an earlier version of IIS, the name is aspnet_wp.exe.
For applications built by using Visual Studio 2005 or later versions, the ASP.NET code can reside on the file system and run under the test server WebDev.WebServer.exe. In that case, you must attach to WebDev.WebServer.exe instead of the ASP.NET process. This scenario applies only to local debugging.
Posted on 6:59 AM by Softminer and filed under
ASP.NET,
Visual Studio
On Server side:
the most important is that the compiled version should be in "Debug" mode because the released version doesnt have the debugging information.
you have to install the "Visual Studio 2008 Service Pack 1 Remote Debugger".
you can download "Visual Studio 2008 Service Pack 1 Remote Debugger" from here
once you have installed it, run the service with "Local Account" authentication. and then run the debugger "rdbgwiz.exe" and allow the users on the domian to connect to the debugger remotly.
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\rdbgwiz.exe
afterward run "MSVSSMON.EXE" as Administrator. otherwise you can not debug "w3wp.exe"
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86\msvsmon.exe
On Developer side:
On Developer side where visual studio is intalled you need to open web Solution with visual studio 2008 and go to Menu debug and attach to debugger and then giving pc name and then connect to w3w.exe
You have to open the project otherwise the debug menu will not show up.
To attach to a running ASP.NET application, you have to know the name of the ASP.NET process:
If you are running IIS 6.0 or IIS 7.0, the name is w3wp.exe.
If you are running an earlier version of IIS, the name is aspnet_wp.exe.
For applications built by using Visual Studio 2005 or later versions, the ASP.NET code can reside on the file system and run under the test server WebDev.WebServer.exe. In that case, you must attach to WebDev.WebServer.exe instead of the ASP.NET process. This scenario applies only to local debugging.
Visual Studio.Net
Post a Comment