I'm developing ASP.NET applications using Visual Studio 2012. I've always used IIS express to test application while developing, but now I need to test it on production environment.
IIS is running on a remote server, I installed there the Remote Debugger studio, created an application under default site (\test\baseTest), created a test project in Visual Studio 2012 and set to "Use Custom Web Server" at path http://myServerName/test/baseTest/
.
Ok, there we are, I press F5 to start debugging, the connection through debugger works correctly (I can see a new line saying "myDomain\myuserName connected" but... the application is void, I miss all .aspx files.
Am i missing something? Should I set some parameters in Visual Studio to deploy all file when debugging to remote site?
Select Configure remote debugging to configure the firewall and start the remote debugger. When configuration is complete, the Remote Debugger window appears. The remote debugger is now waiting for a connection. Use the server name and port number shown to set the remote connection configuration in Visual Studio.
To start debugging, select IIS Express (<Browser name>) or Local IIS (<Browser name>) in the toolbar, select Start Debugging from the Debug menu, or press F5. The debugger pauses at the breakpoints. If the debugger can't hit the breakpoints, see Troubleshoot debugging.
IIS Allows Multiple User to Remote Debug Simultaneously This is one of the most fantastic features of Msvsmon tool. Msvsmon debugging monitor tool allow multiple user to debug simultaneously.
It's usually named something like "w3wp.exe". You do this by going to the "debug" menu in Visual Studio and then selecting "Attach to Process". This brings up a little window with a list of running processes. Finding the IIS process for your application and clicking attach will then start Visual Studio's debugger.
This is remote debugging not automatic deployment.
You should copy all the website files to the remote iis. Remember to build in debug and deploy all the .pdb files. Check also in web.config.
<system.web>
<compilation debug="true" />
</system.web>
Launch the Remote Debugging Monitor (msvsmon.exe) when you start debugging
There you can find a comprehensive guide to remote debugging:
http://www.codeproject.com/Articles/38132/Remote-IIS-Debugging-Debug-your-ASP-NET-Applicatio
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With