The server is never informed when the user closes their browser.
The session_end event is normally called after the server has not gotten any
page requests from the user for 20 minutes (default, configurable in your
web.config).
The Session_End won't fire in a few circumstances, such as when you
end the session prematurely (i.e. pressing the stop button in VS.NET) or if
you aren't using the standard InProc sessions.

Here's more details for you:
[url]http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=7504[/url]

There are some other approaches you can take, such as calling special
session end page from the client side window onclose event.

The Application_End event normally only happens when the server (or IIS) is
shut down.

--
I hope this helps,
Steve C. Orr, MCSD
[url]http://Steve.Orr.net[/url]


"Jim Owen" <jkoseattle@comcast.net> wrote in message
news:unBrFm5VDHA.2008@TK2MSFTNGP11.phx.gbl...
> I am still having trouble getting Application_End to fire from my
> Global.asax file. Now I'm thinking there aren't going to be a huge number
of
> users for this thing, maybe I can just update my DB from Session_End, so
> that it happens as soon as someone closes their browser. Or is that when
> Session_End fires? When does it? And is this a bad thing to do in general?
>
> --
> - Jim Owen
> 206-501-6936
>
>