Cannot debug asp.net website in visual studio

I am not able to debug my website.  When I hit the Start Debugging button in Visual Studio, the project builds and Internet Explorer opens with my site, but Visual Studio does NOT stay in debug mode, it just builds and then starts the website.

I set a breakpoint in my default.aspx page's load event, but it is not hit.  

A while back, I was fiddling with my settings (DUH) and apparently messed something up.  But I have looked over the IIS7 settings and my Visual Studio and project settings and everything makes sense, but I still cannot debug.  What am I doing wrong?

Thanks.
dougschultzAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ajitha75Commented:
Ensure that you have

 <compilation debug="true"/>

in web.config file..

it should be inside <System.Web> element.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tom BeckCommented:
Just wondering if you have rebooted since the problem started. I had the same problem a few days ago and a reboot fixed it.
0
xav056Commented:
Run visual studio as an administrator
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

dougschultzAuthor Commented:
I DO have  <compilation debug="true"/> set in the web.config file.

I HAVE rebooted several times attempting to fix the issue.

I DO run Visual Studio as an administrator.

Still no joy.
0
dougschultzAuthor Commented:
OH, I have made a bit of a breakthrough on this..

I have <location path="." inheritInChildApplications="false" >  wrapping the <system.web> section in my config file.  When I removed this, I was able to debug as expected.

But, why would this be the case?  I do need to have this location tag..

Any ideas?
0
dougschultzAuthor Commented:
Hm, it would appear I've stumbled onto a known issue.

http://bit.ly/cfn0cu

Is anyone able to find any better information on this issue?  Frankly, the workaround stinks.  I'm currently downloading the VS2010 RC to see if that gives any love.
0
Greg GambleProgrammerCommented:

You have this:
<location path="." inheritInChildApplications="false" >

Should it not be:
<location path="/" inheritInChildApplications="false" >

Open in new window

0
dougschultzAuthor Commented:
Apparently not.  It failed with a configuration error:

Parser Error Message: <location> path attribute must be a relative virtual path.  It cannot start with any of ' ' '.' '/' or '\'.
0
Greg GambleProgrammerCommented:
Do you have two apps in the same directory?
0
dougschultzAuthor Commented:
In the production environment I do have nested apps.
0
Greg GambleProgrammerCommented:
But nothing in the development? If so, then why do you need it? Debug works fine without, correct?

Sound like this tag is stopping any writing that the debugger is doing to the web.config.
0
dougschultzAuthor Commented:
Yes, this is the recommended workaround.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Software

From novice to tech pro — start learning today.