>Session_End will can only be used with InProc mode.

Which pretty much makes it useless...

Any half way serious app will want to use StateServer or Sql Server sessions as in ASP.Net the app can and often does get frequently cycled (from Web.config changes to IIS 6's automatic shutdowns) all of which would blow away all InProc Sessions with it.

I'm kind of surprised that this is actually the case. ASP.Net has to have some internal knowledge of hte session since it's serializing it when needed.

But I'm also kind of curious if at Session_End you actually can still get a the session object to be able to serialize the content as Paul wants to do...

+++ Rick ---


>Paul,
>
>Session_End will can only be used with InProc mode.
>
>>>Paul,
>>>
>>>It should be firing when the session expires.
>>>
>>
>>I should have just tested it first (just being lazy, I guess...). Sure enough, it does fire w/o requiring any more hits to the server. That's pretty slick. Do you happen to know if this works for anything besides inproc mode (eg. sqlserver or stateserver)? The docs seem to imply "no".