Skip to main content

Global.asax file explored....

Global.asax

Global.asax file, as the name suggests is a global level(application) level file that contains application wide settings(don not confuse it with web.config settings)

The Global.asax file is in the root application directory.
It's actually an optional file.
It is configured such that it cannot be downloaded.
The ASP.NET page framework recognizes automatically any changes that are made to the Global.asax file.

What happens when this file is changed in a running application?

Answers:The asp.net framework reboots the application.

Now let me explain this reboot thing.In simple and to words the appdomain is restarted.Meaning that all browser sessions will become void, state information is flushed out of the memory.

Developer's Perspective:

The Global.asax file is derived from the HttpApplication class and it maintains a pool of HttpApplication objects, and assigns them to applications as needed.

The Global.asax file contains the following events:

  •  Application_Init: Fired when an application initializes or is first called. It's invoked for all HttpApplication object instances.
  • Application_Disposed: Fired just before an application is destroyed. This is the ideal location for cleaning up previously used resources.
  •  Application_Error: Fired when an unhandled exception is encountered within the application.
  •  Application_Start: Fired when the first instance of the HttpApplication class is created. It allows you to create objects that are accessible by all HttpApplication instances.
  • Application_End: Fired when the last instance of an HttpApplication class is destroyed. It's fired only once during an application's lifetime.
  • Application_BeginRequest: Fired when an application request is received. It's the first event fired for a request, which is often a page request (URL) that a user enters.
  •  Application_EndRequest: The last event fired for an application request.
  •  Application_PreRequestHandlerExecute: Fired before the ASP.NET page framework begins executing an event handler like a page or Web service.
  •  Application_PostRequestHandlerExecute: Fired when the ASP.NET page framework is finished executing an event handler.
  • Applcation_PreSendRequestHeaders: Fired before the ASP.NET page framework sends HTTP headers to a requesting client (browser).
  •  Application_PreSendContent: Fired before the ASP.NET page framework sends content to a requesting client (browser).
  •  Application_AcquireRequestState: Fired when the ASP.NET page framework gets the current state (Session state) related to the current request.
  •  Application_ReleaseRequestState: Fired when the ASP.NET page framework completes execution of all event handlers. This results in all state modules to save their current state data.
  •  Application_ResolveRequestCache: Fired when the ASP.NET page framework completes an authorization request. It allows caching modules to serve the request from the cache, thus bypassing handler execution.
  •  Application_UpdateRequestCache: Fired when the ASP.NET page framework completes handler execution to allow caching modules to store responses to be used to handle subsequent requests.
  •  Application_AuthenticateRequest: Fired when the security module has established the current user's identity as valid. At this point, the user's credentials have been validated.
  •  Application_AuthorizeRequest: Fired when the security module has verified that a user can access resources.
  •  Session_Start: Fired when a new user visits the application Web site.
  •  Session_End: Fired when a user's session times out, ends, or they leave the application Web site.


To take the real  advantage of the events knowledge of the  order in which they're triggered is critical. 
The Application_Init and Application_Start events are fired once when the application is first started. Likewise, the Application_Disposed and Application_End are only fired once when the application terminates. In addition, the session-based events (Session_Start and Session_End) are only used when users enter and leave the site. 
The remaining events deal with application requests, and they're triggered in the following order:

  • Application_BeginRequest
  • Application_AuthenticateRequest
  • Application_AuthorizeRequest
  • Application_ResolveRequestCache
  • Application_AcquireRequestState
  • Application_PreRequestHandlerExecute
  • Application_PreSendRequestHeaders
  • Application_PreSendRequestContent
  • << The application code  executes>>
  • Application_PostRequestHandlerExecute
  • Application_ReleaseRequestState
  • Application_UpdateRequestCache
  • Application_EndRequest

I wish I could provide an example, butting short time....
Hope it was helpful.
Till next we connect.....Happy Coding
 
Labels:

Comments

Post a Comment

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more

WPF Overview-Part-II

This post is in continuation to the last post. In this Post I’ll be exploring the Dependency Properties Dependency properties are similar to CLR properties with more advanced and complex features. The main difference between the CLR properties and dependency properties is, that the value of a normal .NET property is read directly from a private member in your class, whereas the value of a DependencyProperty is resolved dynamically when calling the GetValue() method that is inherited from DependencyObject . In case this description did not make sense, no need to worry, It will become clear by the time you reach end of this article. How the Value is Resolved in Dependency properties Every time a dependency property is accessed, it internally resolves the value by following the precedence from high to low. It checks if a local value is available, if not, check if a custom style trigger is active and I the similar manner continues until it finds a value. At last the default value is alwa...
Post a Comment
Read more

WebMatrix-The Swiss Army knife from Microsoft

  What’s more in store for Web developers, ASP.Net 4.5(with full support for HTML 5 , CSS 3 amd Javascript) and to complement it, is the new awesome tool-WebMatrix. WebMatrix combines five products in one, letting you install, develop, optimize, deploy and manage your sites and databases. With support for the latest web standards like HTML5 & CSS3, multiple frameworks like ASP.NET & PHP, and multiple database engines like MySQL & SQL Server ..and what’s even better…it FREE!! ! ( Download Webmatrix ). To learn more about webmatrix, I recomment the following video. WebMatrix-An intro The tools promises a lot and I have already downloaded a copy and started playing with it. Hope the information  here is useful. Till next we connect…. Happy Learning.
Post a Comment
Read more