.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Articles >> ASP.NET >> Post New Resource Bookmark and Share   

 Subscribe to Articles

What are major events in GLOBAL.ASAX file ?

Posted By:Shashi Ray       Posted Date: March 20, 2009    Points: 25    Category: ASP.NET    URL: http://www.dotnetspark.com  
 

 

The Global.asax file, which is derived from the HttpApplication class, 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 is 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 is fired only once during an application's lifetime.

 

Application_BeginRequest: Fired when an application request is received. It is 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 has 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 send 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.

 

 

Shashi Ray


 Subscribe to Articles

     

Further Readings:

Responses

No response found. Be the first to respond this post

Post Comment

You must Sign In To post reply
Find More Articles on C#, ASP.Net, Vb.Net, SQL Server and more Here

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend