I'm developing an ASP.NET site off of my Windows XP IIS Installation, and whenever I tell visual studio to attach-to-process to the aspnet_wp.exe it starts a new instance of asp.net development server. Is there a way to make it not start asp.net development server since I don't need it to launch anything?
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.
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.
Open Visual Studio in Administrator Mode, then Debug -> attach to process -> tick the check box "Show processes from all user", select w3wp.exe. Administration mode is required for debugging the source code.
With the app running, in Visual Studio, select Debug > Attach to Process. In the Attach to Process dialog, type the first letters of process names from the following list, or enter them into the search box. The one that is running is the one running the ASP.NET app. Attach to that process to debug the app.
If you want to turn that off all you have to do is change the settings on the project file (using f4 to show the property grid). There is an option that says Always Start When Debugging, set that to false and you should be fine.
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