Take the 2-minute tour ×  Let's collect some tips for evaluating
the appropriate use of global.asax.  share|improve this question
closed as not constructive by Bill the Lizard Aug 8 '12 at 19:40
Personally, I don't think a global.asax tag is needed... – 
Jason Bunting Sep 25 '08 at 20:12 Fair enough, I'll remove that
comment as well –  Larsenal Sep 25 '08 at 20:26  10 Answers 10
up vote 3 down vote accepted  It's simple to use if your session
and application initialization code is very small and
application-specific. Using an HttpModule is more useful if you
want to reuse code, such as setting up rules for URL rewriting,
redirects or auth. An HttpModule can cover everything a
Global.asax file can. They can also be removed and added easily
using your .config.  share|improve this answer  I've used it
before to catch errors at the application level, and to do
something when a user's session expires.  I also tend to use it
a lot to provide static properties that read values from the
web.config.  I think it ok