The Global Application Class has changed in ASP.NET 2.0. When
adding a Global Application Class to a project, Visual Studio no longer
generates a code-behind file.
The result as Ross Nelson points out is two fold: there is
no class in the Global.asax, and without the class there is no "easy" way to reference Global routines / objects.
I’ve long been a fan of wrapping application globals into
Access Routines, creating one static instance of the class, then accessing these
routines through the Global class.
Ross has an excellent solution to this problem:
(Fixing the Global.asax in ASP.NET 2.0).