| Subject: F5 stopped attaching the debugger automatically |
| Group: microsoft.public.vstudio.general |
| Date: 8/20/2008 12:55:43 AM |
| From: nospam@nospam.sss (John Dalberg) |
Using VS 2008 SP1 with an ASP.NET project. Suddenly I lost the ability to automatically have the debugger attached automatically when I run in debug mode (F5). I have 'ASP.NET' checked in the project properties->Web section. Integrated Windows authentication is checked in IIS. debug is enabled in web.config. I don't get any errors. I have this issue whether I am using IIS or the VS web server. Manually attaching the debugger works but I need to restore the ability to run in debug mode as I always had been. John Dalberg |
| Back |
| Subject: Re: F5 stopped attaching the debugger automatically |
| Group: microsoft.public.vstudio.general |
| Date: 8/20/2008 8:59:24 PM |
| From: nospam@nospam.sss (John Dalberg) |
nospam@nospam.sss (John Dalberg) wrote: > Using VS 2008 SP1 with an ASP.NET project. > > Suddenly I lost the ability to automatically have the debugger attached > automatically when I run in debug mode (F5). I have 'ASP.NET' checked in > the project properties->Web section. Integrated Windows authentication is > checked in IIS. debug is enabled in web.config. I don't get any errors. I > have this issue whether I am using IIS or the VS web server. Manually > attaching the debugger works but I need to restore the ability to run in > debug mode as I always had been. > Ok I found out that the problem is because I have a <location> surrounding <system.web> as in <location path="." inheritInChildApplications="false"> As I remember having this pre SP1 caused the behavior mentioned in this url: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Feedb ackID=327456 Basically it created another <system.web> which had <compilation debug="true" defaultLanguage="c#"> in it instead of adding it in the first <system.web>. Actually the first <system.web> had it but the parser is not parsing corectly. This caused the web.config to have two <system.web> sections! So it seems in SP1 the debugger just doesn't run. So what the heck is this? A fix that seems to be a bad hack just to get rid of the behavior? John Dalberg |
| Back |
| Subject: Re: F5 stopped attaching the debugger automatically |
| Group: microsoft.public.vstudio.general |
| Date: 9/4/2008 9:54:19 PM |
| From: nospam@nospam.sss (John Dalberg) |
nospam@nospam.sss (John Dalberg) wrote: > nospam@nospam.sss (John Dalberg) wrote: > > Using VS 2008 SP1 with an ASP.NET project. > > > > Suddenly I lost the ability to automatically have the debugger attached > > automatically when I run in debug mode (F5). I have 'ASP.NET' checked > > in the project properties->Web section. Integrated Windows > > authentication is checked in IIS. debug is enabled in web.config. I > > don't get any errors. I have this issue whether I am using IIS or the > > VS web server. Manually attaching the debugger works but I need to > > restore the ability to run in debug mode as I always had been. > > > > Ok I found out that the problem is because I have a <location> > surrounding <system.web> as in > <location path="." inheritInChildApplications="false"> > > As I remember having this pre SP1 caused the behavior mentioned in this > url: > https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?Fee > db ackID=327456 > > Basically it created another <system.web> which had <compilation > debug="true" defaultLanguage="c#"> in it instead of adding it in the > first <system.web>. Actually the first <system.web> had it but the parser > is not parsing corectly. This caused the web.config to have two > <system.web> sections! > > So it seems in SP1 the debugger just doesn't run. So what the heck is > this? A fix that seems to be a bad hack just to get rid of the behavior? > Is there anyone in the VS team who can verify this or should I take it as a fact that this is a problem? John Dalberg |
| Back |