problem with aspnet exiting

[Bonj]

When trying to debug an ASP.NET project by placing a breakpoint in one of the
functions in the codebehind, VS correctly stops at the breakpoint, and I can
step through. But soon after, the process stops dead and can't be stepped
through anymore (even though there is no error) - I'm guessing that the
aspnet_wp.exe is detecting that if it's inactive for a period of n seconds or
so, then it exits until it gets another request.

Is there anyway of making it not do this, as it means I can only debug for a
maximum of about 20 seconds!

[Jim Cheshire [MSFT]]

Hi Bonj,

Do you see anything from ASP.NET in the Application log?

Jim Cheshire [MSFT]
MCP+I, MCSE, MCSD, MCDBA
ASP.NET Developer Support
ja******@online.microsoft.com

This post is provided "AS-IS" with no warranties and confers no rights.

--------------------
| Thread-Topic: problem with aspnet exiting
| thread-index: AcTIAcbUsZqSE9kISpOoVf8/0jMFaA==
| X-WBNR-Posting-Host: 193.130.149.130
| From: "=?Utf-8?B?Qm9uag==?=" <Bo**@discussions.microsoft.com>
| Subject: problem with aspnet exiting
| Date: Thu, 11 Nov 2004 07:19:02 -0800
| Lines: 9
| Message-ID: <D3**********************************@microsoft.co m>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups:
microsoft.public.dotnet.framework.aspnet,microsoft .public.dotnet.languages.c
sharp
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
| Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.languages.csharp:285995
microsoft.public.dotnet.framework.aspnet:275339
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| When trying to debug an ASP.NET project by placing a breakpoint in one of
the
| functions in the codebehind, VS correctly stops at the breakpoint, and I
can
| step through. But soon after, the process stops dead and can't be stepped
| through anymore (even though there is no error) - I'm guessing that the
| aspnet_wp.exe is detecting that if it's inactive for a period of n
seconds or
| so, then it exits until it gets another request.
|
| Is there anyway of making it not do this, as it means I can only debug
for a
| maximum of about 20 seconds!
|

[Jeff Dillon]

So your browser is still open, yet the debugger stops?

The debugger usually stops as soon as you close the browser session.

Jeff

"Bonj" <Bo**@discussions.microsoft.com> wrote in message
news:D3**********************************@microsof t.com...

When trying to debug an ASP.NET project by placing a breakpoint in one of the functions in the codebehind, VS correctly stops at the breakpoint, and I can step through. But soon after, the process stops dead and can't be stepped
through anymore (even though there is no error) - I'm guessing that the
aspnet_wp.exe is detecting that if it's inactive for a period of n seconds or so, then it exits until it gets another request.

Is there anyway of making it not do this, as it means I can only debug for a maximum of about 20 seconds!

[Bonj]

> So your browser is still open, yet the debugger stops?

I've noticed it do that before, yes. Isn't doing at the moment though...
don't want to speak too soon, but touch wood it might not try any funny
business.

"Jeff Dillon" <je**@removeemergencyreporting.com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...

The debugger usually stops as soon as you close the browser session.

Jeff

"Bonj" <Bo**@discussions.microsoft.com> wrote in message
news:D3**********************************@microsof t.com...

When trying to debug an ASP.NET project by placing a breakpoint in one of

the

functions in the codebehind, VS correctly stops at the breakpoint, and I

can

step through. But soon after, the process stops dead and can't be stepped
through anymore (even though there is no error) - I'm guessing that the
aspnet_wp.exe is detecting that if it's inactive for a period of n
seconds

or

so, then it exits until it gets another request.

Is there anyway of making it not do this, as it means I can only debug
for

a

maximum of about 20 seconds!