Cannot debugging asp.net on IIS7 by attaching process w3wp

asp.net debugging iis-7 w3wp
max picture max · Mar 7, 2011 · Viewed 9.6k times · Source

I have a asp.net website in VS2008 which I have pre-compiled in local directory which is virtual directory for IIS 7（http://machinename:83）

when i 1. launch http://machinename:83/ 2. VS2008-->debug-->Attach to Process..-->select w3wp.exe 3. set the breakpoint in code in VS2008 4. run app

while i found it cannot go to the breakpoint. (i m sure the breakpoint must be run)

anybody can help me on this?

Answer

Josh Pearce picture Josh Pearce · Mar 7, 2011

What you're doing should work, but you can try this, which is frequently used to debug Windows services upon startup:

System.Diagnostics.Debugger.Launch();

Just put it on the line where you want to start debugging, and the OS will prompt you to attach.

Related questions

A process serving application pool 'X' suffered a fatal communication error with the Windows Process Activation Service

I'm running an ASP.NET 4.0 application under IIS 7.5. Several times a day, our application pool is recycling unexpectedly. Our system log shows the following event when this occurs: A process serving application pool 'X' suffered a fatal communication error with …

Read More
The breakpoint will not currently be hit. No symbols have been loaded for this document in a Silverlight application

Ok, what I have: Visual Studio 2010 RC, W7 x64, started a new project type of Silverlight application. Hosting the Silverlight application in a ASP.NET Web Application Project. Silverlight Version 3.0. Added a LinqToSQL Class, a WCF Service, a Winform Tester …

Read More
Stop Visual Studio from launching a new browser window when starting debug?

I already have a window open with the web site I'm debugging. I don't need VS to launch another one for me every time I need to debug. Is there a way to stop this behavior?

Read More