Hi Charles,

I had the same problem.  I was using VSS as the sourcecontrol for my 
project, and the problem went away when I checked the webconfig file for 
project in.  Whenever the file was checked out and I tried to debug, I 
would get the same error message as you did.

Hope that helps,

Schalk

> Thanks Mike.  I deleted all dll's & pdb's.  That did not work, else it 
was
not enough.  I next started removing from the solution recent pages.  That
seems to do the trick.  Then I slowly added the pages back, checking the
debug capability with each new page.  I'm OK now.

FYI:  The MSDN knowledge base contained an entry for this condition.  It's
solution was to reset IIS with iisreset.exe from the dos prompt.  That did
not do a thing for me.

.NET is nice technology, but VS.NET is buggy.  Maybe next release will
stablize some.


----- Original Message -----
From: "Mike Gale" <info@d...>
To: "Website Programming with ASP.NET"
<aspdotnet_website_programming@p...>
Sent: Monday, October 21, 2002 8:00 PM
Subject: [aspdotnet_website_programming] RE: Newbie debugging help


> Charles Walsek wrote:
> > Do you know to recover from this dialog box while debugging:
> >
> > Microsoft Development Environment-  Error while trying to run project:
> > Unable to start debugging on the web server.  System call failed.
> > Would you like to disable future attempts to debug ASP.NET pages for
> > this project?
> >
> > I can debug other projects, but no longer ThePhile.  I was working on
> > incorporating the Polls Module into the project when I encountered the
> > error.  I've tried rebooting and rebuilding, w/o success.  All I can
> > come up with now is to begin another solution and bring the code in,
> > one project at a time.  Seems like there ought to be an easier way.
> > Comments anyone?
>
> I've not had this exact message but I have had VS give me BSE's (Blue
> Screen Events).  This appears to be associated with compiling in debug
> mode.
>
> A cycle to identify the cause takes longer than the fix so I now simply
> take both actions I've identified in the past.
>
> 1)  Delete all dll's and pdb's.  After doing that check that they are
> actually gone.  I had one that couldn't be deleted, but it could be
> renamed and moved so I did that.  (If you have external dll's in bin
> leave these!)
>
> 2)  Compile each component project starting at those with no
> interproject dependencies (In thePhile Core first) and work towards
> those that have dependencies (in thePhile the ASP.NET project).
>
> This fixes my problems.
>
> I've also noted that sometimes a wait of a few minutes does the trick.
> (Does not fix "BSE faults".)
>
> My sense is that VS struggles when it has a lot of projects (maybe
> exacerbated by debug mode) to deal with.  If you can drop projects from
> a solution after those projects have gone to release things speed up.
>
> Mike Gale, Decision Engineering (NZ) Ltd.
>
>