Remote debugging is the one of the most challenging things to accomplish.
To remote debug.
1. Check visual studio version, to do this go to Help -> About mine is "Microsoft Visual Studio 2010 Ultimate".
2. Google for "Microsoft Visual Studio 2010 remote debugger download"
3. Download the 64 bit installer from the Microsoft website e.g.
http://www.microsoft.com/en-gb/download/details.aspx?id=475
4. The one I needed to download was 64 bit and called "rdbgsetup_x64.exe"
5. Install the installer on the server where the web service is running
6. On the start enter 'remote debugger' and then right click the 'Visual Studio Remote Debugging Monitor (x64) from the list of available options and select to run under 'Run as Administrator'
7. In the remote debugger go to 'Tool -> Options' and select 'No Authentication (native only) and also check 'Allow any user to debug' then copy the name from Server name at top e.g. 'TempServerbox01:4015'
8. Disable Firewall on this server
9. Go to dev box and go to tool-> Attach to process option
10. select following value from the opened 'Attach to Process'
Transport: Remote (Nateive only with no authentication)
Qualifier: TempServerbox01:4015
click on refresh button and then select wp.exe/
11. Remote debugging is all set.
No if at the break point you are getting the message of "The breakpoint will not currently be hit", Then perform following steps.
1. Turn off firewall at dev box as well as at server where the webservice is deployed, as remote debugging process will try to send and receive request at both sides
2. Where remote debugger is running, change the Authentication mode to Windows Authentication, and copy the server name value e.g. abc\kaleemkhan@TempServerBox1
3. On the dev box open the attach to process window and enter following values
Transport: Default
Qualifier: abc\kaleemkhan@TempServerBox1
4. Select any wp.exe present.
Remote debugging is all set now.
Disclaimer.
I take no responsibility of above mentioned instructions and any repercussions whatsoever as firewall should never be stopped and also remote debugger should be running under authentication which off course clearly I have not abide.
To remote debug.
1. Check visual studio version, to do this go to Help -> About mine is "Microsoft Visual Studio 2010 Ultimate".
2. Google for "Microsoft Visual Studio 2010 remote debugger download"
3. Download the 64 bit installer from the Microsoft website e.g.
http://www.microsoft.com/en-gb/download/details.aspx?id=475
4. The one I needed to download was 64 bit and called "rdbgsetup_x64.exe"
5. Install the installer on the server where the web service is running
6. On the start enter 'remote debugger' and then right click the 'Visual Studio Remote Debugging Monitor (x64) from the list of available options and select to run under 'Run as Administrator'
7. In the remote debugger go to 'Tool -> Options' and select 'No Authentication (native only) and also check 'Allow any user to debug' then copy the name from Server name at top e.g. 'TempServerbox01:4015'
8. Disable Firewall on this server
9. Go to dev box and go to tool-> Attach to process option
10. select following value from the opened 'Attach to Process'
Transport: Remote (Nateive only with no authentication)
Qualifier: TempServerbox01:4015
click on refresh button and then select wp.exe/
11. Remote debugging is all set.
No if at the break point you are getting the message of "The breakpoint will not currently be hit", Then perform following steps.
1. Turn off firewall at dev box as well as at server where the webservice is deployed, as remote debugging process will try to send and receive request at both sides
2. Where remote debugger is running, change the Authentication mode to Windows Authentication, and copy the server name value e.g. abc\kaleemkhan@TempServerBox1
3. On the dev box open the attach to process window and enter following values
Transport: Default
Qualifier: abc\kaleemkhan@TempServerBox1
4. Select any wp.exe present.
Remote debugging is all set now.
Disclaimer.
I take no responsibility of above mentioned instructions and any repercussions whatsoever as firewall should never be stopped and also remote debugger should be running under authentication which off course clearly I have not abide.
