Event Handlers Gone Wild

re: Event Handlers Gone Wild

Bill Pierce — Thu, 07 Sep 2006 00:20:14 GMT

Todd,
Thanks for the post. Almost wandered down the path of Tess's customer. My apps are so small I probably wouldn't have noticed. I didn't know ASP.Net will spawn more than one HttpApplication.

Thanks,
-Bill

Link Listing - September 6, 2006

Christopher Steen — Thu, 07 Sep 2006 05:36:51 GMT

More on Atlas [Via: James Avery ] Smart Client Deployment with ClickOnce - Final Manuscript Complete!...

re: Event Handlers Gone Wild

Bill Pierce — Thu, 07 Sep 2006 18:11:03 GMT

Todd,
You're post got me thinking about additional questions.

If ASP.Net spawns a new HttpApplication, does the Application_Start event fire for the new HttpApp?

When the load dies down and the additional HttpApplication is no longer needed, does it just get GC'd? Does the Application_End event fire?

Thanks for the knowledge.

re: Event Handlers Gone Wild

Toddca — Fri, 08 Sep 2006 22:55:47 GMT

Good question Bill. The Application_Start event only fires on the first instance of an HttpApplication being created and the Application_End will only fire on the destruction of the last HttpApplication instance.

You could argue (and I would probably agree) that a better solution would have been to register for the event in the Application_Start event handler.