Web Application Setting in ASP.NET: Global.asax

Storing the settings of your ASP.NET application in the Global.asax file is the easiest way. This solution is based on using the Application_Start method and global property Application.
The Application property of HttpContext class returns HttpApplicationState object for the current HTTP request. HttpApplicationState object allows sharing of global parameters between multiple sessions and requests with you ASP.NET application.

A single instance of an HttpApplicationState class is created the first time a client requests any URL resource from within a particular ASP.NET application virtual directory. A separate single instance is created for each ASP.NET application on a Web server. A reference to each instance is then exposed via the intrinsic HttpContext.Application object.

Method Application_Start occurs as the first event in the HTTP pipeline chain of execution when ASP.NET responds to a request.

Review the following example:

Global.asax.cs

protected void Application_Start(Object sender, EventArgs e)
{

Application["DbUser"]="dbUser";

Application["DbUserPass"]="myPass";

Application["DbName"]="coolDB";

Application["DbServer"]="my.office.db.server";

string myConnString = "Data Source=" +Application["DbServer"] + ";Initial Catalog=" +Application["DbName"] + ";User ID=" +Application["DbUser"] + ";Password=" +Application["DbUserPass"];

Application["ConnString"] = myConnString;
}

Thus when your web application starts the Application object will contain the values of your parameters and you can access them on page within your application.

SomePage.asax.cs

private void Page_Load(object sender, System.EventArgs e)
{

SqlConnection myCnn;

SqlCommand myCmd;

SqlDataReader myReader;

myCnn = new SqlConnection((string)Application["ConnString"]);

myCmd = new SqlCommand("select * from countries", myCnn);

myCnn.Open();

myReader = myCmd.ExecuteReader();

// :

// Do something

// :

myCnn.Close();
}

Let's consider the advantages and disadvantages of using Global.asax as storage for web application parameters.
Advantages:

Simplicity of realization
You can store the critical parameters, which you don't want to be changed without your confirmation (Developer Name, License Information). The changing of any parameter within Global.asax file requires recompilation of whole application. So it will be impossible to do without an access to source code
Disadvantages:

To change the value of any parameter it is required to recompile whole application. Therefore this method is not good for parameters, which have to be changed frequently.
Uploading of recompiled version will cause restart of whole application.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Exploring the Global.asax file in ASP.NET

 

Have you ever felt the need of writing logic at the application level; precisely a location or a file where you could handle events or errors at the application level? Well if yes, then enter the Global.asax. Using this file, you can define event handlers with application-wide or session-wide scope. In this article, we will explore the application and session level events exposed in the Global.asax file and how we can utilize these events in our applications.

The Global.asax, also known as the ASP.NET application file, is located in the root directory of an ASP.NET application. This file contains code that is executed in response to application-level and session-level events raised by ASP.NET or by HTTP modules. You can also define ‘objects’ with application-wide or session-wide scope in the Global.asax file. These events and objects declared in the Global.asax are applied to all resources in that web application.

Note 1: The Global.asax is an optional file. Use it only when there is a need for it.

Note 2: If a user requests the Global.asax file, the request is rejected. External users cannot view the file.

The Global.asax file is parsed and dynamically compiled by ASP.NET. You can deploy this file as an assembly in the \bin directory of an ASP.NET application.

How to create Global.asax

Adding a Global.asax to your web project is quiet simple.

Open Visual Studio 2005 or 2008 > Create a new website > Go to the Solution Explorer > Add New Item > Global Application Class > Add.

Examining the methods related to the events in Global.asax

There are 2 ‘set’ of methods that fire corresponding to the events. The first set which gets invoked on each request and the second set which does not get invoked on each request. Let us explore these methods.

Methods corresponding to events that fire on each request

Application_BeginRequest() – fired when a request for the web application comes in.

Application_AuthenticateRequest –fired just before the user credentials are authenticated. You can specify your own authentication logic over here.

Application_AuthorizeRequest() – fired on successful authentication of user’s credentials. You can use this method to give authorization rights to user.

Application_ResolveRequestCache() – fired on successful completion of an authorization request.

Application_AcquireRequestState() – fired just before the session state is retrieved for the current request.

Application_PreRequestHandlerExecute() - fired before the page framework begins before executing an event handler to handle the request.

Application_PostRequestHandlerExecute() – fired after HTTP handler has executed the request.

Application_ReleaseRequestState() – fired before current state data kept in the session collection is serialized.

Application_UpdateRequestCache() – fired before information is added to output cache of the page.

Application_EndRequest() – fired at the end of each request

Methods corresponding to events that do not fire on each request

Application_Start() – fired when the first resource is requested from the web server and the web application starts.

Session_Start() – fired when session starts on each new user requesting a page.

Application_Error() – fired when an error occurs.

Session_End() – fired when the session of a user ends.

Application_End() – fired when the web application ends.

Application_Disposed() - fired when the web application is destroyed.

Show me an example!!

Let us see an example of how to use the Global.asax to catch unhandled errors that occur at the application level.

To catch unhandled errors, do the following. Add a Global.asax file (Right click project > Add New Item > Global.asax). In the Application_Error() method, add the following code: 

C#

 void Application_Error(object sender, EventArgs e)

    {

        // Code that runs when an unhandled error occurs

        Exception objErr = Server.GetLastError().GetBaseException();

        string err = "Error in: " + Request.Url.ToString() +

                          ". Error Message:" + objErr.Message.ToString();

       

    }

VB.NET

Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)

        ' Code that runs when an unhandled error occurs       

        Dim objErr As Exception = Server.GetLastError().GetBaseException()

        Dim err As String = "Error in: " & Request.Url.ToString() & ". Error Message:" & objErr.Message.ToString()

       

    End Sub

Here we make use of the Application_Error() method to capture the error using the Server.GetLastError().

Conclusion:

In this article, we learnt that Global.asax is a file used to declare application-level events and objects. The file is responsible for handling higher-level application events such as Application_Start, Application_End, Session_Start, Session_End, and so on. I would encourage you to explore the methods corresponding to the events and analyze the best possible methods to use them in your application, if needed.

I hope you liked the article and I thank you for viewing it.