ok ... so...

Thanks both of you for your replies, I assume you are both talking about the
session timeout at this point...
If so...its currently set to 20 minutes, I had *assumed* that this was only
relevant when setting session variables though - something that I do not use
in this application.
I have about 5 user controls which build up the page.
About 10 functions in total perhaps, one works out what page the user is on,
one display and image based on that, one changes hex to dec for colour codes
(see my other thread entitled - Setting table cell colors) - the others are
primarily for building tables dynamically.
Some add rows, some add cells...thats about it...
hmm...still a bit unsure what might be causing it now...its currently
still in 'debug' mode - I've not done a 'release' mode version yet - could
that be anything to do with it?
Thanks again for any help.
Regards
Robwhen you first hit an asp.net site, loads a new appdomain, then loads the
asp.net dll for that page (one per page). if the dll does not exist it
compiles it first.
if site has had no activity for a given amount of time (idle - see
machine.config), the app domain is unloaded, and the next hit causes the
above to repeat.
-- bruce (sqlwork.com)
"Rob Meade" <robb.meade@.NO-SPAM.kingswoodweb.net> wrote in message
news:_n2xc.240$Js2.2394304@.news-text.cableinet.net...
> Thanks both of you for your replies, I assume you are both talking about
the
> session timeout at this point...
> If so...its currently set to 20 minutes, I had *assumed* that this was
only
> relevant when setting session variables though - something that I do not
use
> in this application.
> I have about 5 user controls which build up the page.
> About 10 functions in total perhaps, one works out what page the user is
on,
> one display and image based on that, one changes hex to dec for colour
codes
> (see my other thread entitled - Setting table cell colors) - the others
are
> primarily for building tables dynamically.
> Some add rows, some add cells...thats about it...
> hmm...still a bit unsure what might be causing it now...its currently
> still in 'debug' mode - I've not done a 'release' mode version yet - could
> that be anything to do with it?
> Thanks again for any help.
> Regards
> Rob
>
AFAIK, in ASP classic, the application shutdown when the last session
terminates (and the last session terminates once the timeout is reached
without any request from the user). Check also Marina adivces as ASP.NET
could perhaps provides another setting that make the application still waits
an aditional amount of time before shuting down...
Note also that the application is also restarted when the application is
updated...
I'm not sure how the user contrrols are related to this. Are you talking
about the same problm ? If a separate problem you may want to open another
discussion thread...
Patrice
"Rob Meade" <robb.meade@.NO-SPAM.kingswoodweb.net> a crit dans le message de
news:_n2xc.240$Js2.2394304@.news-text.cableinet.net...
> Thanks both of you for your replies, I assume you are both talking about
the
> session timeout at this point...
> If so...its currently set to 20 minutes, I had *assumed* that this was
only
> relevant when setting session variables though - something that I do not
use
> in this application.
> I have about 5 user controls which build up the page.
> About 10 functions in total perhaps, one works out what page the user is
on,
> one display and image based on that, one changes hex to dec for colour
codes
> (see my other thread entitled - Setting table cell colors) - the others
are
> primarily for building tables dynamically.
> Some add rows, some add cells...thats about it...
> hmm...still a bit unsure what might be causing it now...its currently
> still in 'debug' mode - I've not done a 'release' mode version yet - could
> that be anything to do with it?
> Thanks again for any help.
> Regards
> Rob
>
No, nothing to do with sessions. This is a timeout on the asp applications -
the amount of time no one makes any requests.
"Rob Meade" <robb.meade@.NO-SPAM.kingswoodweb.net> wrote in message
news:_n2xc.240$Js2.2394304@.news-text.cableinet.net...
> Thanks both of you for your replies, I assume you are both talking about
the
> session timeout at this point...
> If so...its currently set to 20 minutes, I had *assumed* that this was
only
> relevant when setting session variables though - something that I do not
use
> in this application.
> I have about 5 user controls which build up the page.
> About 10 functions in total perhaps, one works out what page the user is
on,
> one display and image based on that, one changes hex to dec for colour
codes
> (see my other thread entitled - Setting table cell colors) - the others
are
> primarily for building tables dynamically.
> Some add rows, some add cells...thats about it...
> hmm...still a bit unsure what might be causing it now...its currently
> still in 'debug' mode - I've not done a 'release' mode version yet - could
> that be anything to do with it?
> Thanks again for any help.
> Regards
> Rob
>
Marina,
I'm a bit by this value.
How does it behave compared with the session timeout ? Does it restart using
this value (shutdown possibly session even if the session timeout value is
greater) or is this some additional amount of time ?
I suppose ASP.NET still ends the app when there is no more sessions (even
when this value is infinite) ?
Thanks in advance for any pointers (so far the doc I've saw is not crystal
clear)
Patrice
"Marina" <someone@.nospam.com> a crit dans le message de
news:%23XwiXMMTEHA.3336@.TK2MSFTNGP12.phx.gbl...
> No, nothing to do with sessions. This is a timeout on the asp
applications -
> the amount of time no one makes any requests.
> "Rob Meade" <robb.meade@.NO-SPAM.kingswoodweb.net> wrote in message
> news:_n2xc.240$Js2.2394304@.news-text.cableinet.net...
> the
> only
> use
> on,
> codes
> are
could
>