2 Hadar |
Wednesday, March 01, 2006 @ 1:12 AM
Very nice article. it clear things up.
I was also wondering why global works like this - it is really a bad implemention.
3 Jørn Schou-Rode |
Saturday, May 20, 2006 @ 9:02 AM
"so VBScript-ish, so loosely–typed"
I think you are absolutely right! I tend to do handle all application events through HttpModules instead, which also helps to keep different functionalities apart.
4 Nick |
Wednesday, September 20, 2006 @ 4:53 AM
It was probably implemented so "VBScript-ish" to support the ability to upgrade an ASP site to ASP.NET by people who are still learning ASP.NET.
5 Mike |
Monday, September 10, 2007 @ 1:06 AM
How else would you wire these events up, through an HttpModule? That may be correct, but it may also be 'too difficult' for many VB programmers, and MS wants to help them by giving them an easy way to hook these events.
And hooking up the session events is even more difficult without global.asax
6 WC |
Tuesday, October 02, 2007 @ 12:45 PM
It's a just a quick, convenient way to wire up stuff. It's obviously an aid to upgrades from classic asp. Don't like it? Write a module and delete the file. Poof, problem solved.
7 Daniel Williams |
Thursday, August 07, 2008 @ 7:45 AM
This was a great summary. Thank you for delving into it and distilling it into a short, concise article.
Submit your comment
Please enter only text since all HTML tags except hyperlinks will be stripped.
Hyperlinks will become live links. Any comments with flaming or offensive language will be
deleted. Be courteous to other posters. Thank you.
