My brief search for an economical (ASP.NET 2.0) journal (weblog) revealed a couple popular options: dasBlog, Community Server 2.0, Drupal, and .Text.
Community Server 2.0 had a couple flavors ranging from: a free (restricted) Express edition, through to an Enterprise edition.
After struggling with Community Server documentation and already being weary of “free” editions – as they usually have a catch somewhere – I moved onto the next option.
dasBlog a free, BSD-licensed weblog engine for the .NET Framework. I downloaded compiled and installed dasBlog, it worked, and met my requirements . Now – thanks to the dasBlog contributors – I can move on.
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).
For a summarized (distilled) version of Ross's article view: Distilled: Fixing the Global.asax in ASP.NET 2.0