tehehe, i think its a bug :-). It's not actually, i'm having fun here
because a few moons ago i was convinced of that same thing until someone
taught me. I'm passing on what i've learned if you promise to do the same
when it is your turn.
what you have done so far doesn't guarantee that the end event will be
called. I wager that even if you shut down visual studio and bring it back
up, the application_end still won't fire. That's by design to mimic the
behavior of a production environment.
Here is how to trigger it. Put a break point in the application_end event
and run the application. Leave visual studio running minimized. Use notepad
to open the webconfig file, make an immaterial change to the web config file
and push save. Behold as the culprit is caught and exposed.
Here is the explanation: Your webpages run inside of an application object.
Do not confuse your web page with the application object. There really is
only limited dependency on the two. The webpage you see on screen in the
browser may initialize the application object if the application object
isn't already started because an application object is required. When you
close the browser, the application object is still running so the end event
won't fire. A few things can kill the application object causing its end
event to be fired. A dirty web config file (which we tried), a dirty global
asax file, a dirty assembly, iis resets. You didn't do any of those so the
end event wasn't being triggered.
--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/3he3b
"Junior_BR" <(E-Mail Removed)> wrote in message
news:5039057A-C6DD-4296-8976-(E-Mail Removed)...
> I have closed the browser and the Event doesn't fire... I have change to
another page, and the event doesn't fires too... I think the application
it's realy ended, and the event realy don't works...
Similar Threads
