Global.aspx file in asp.net

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. 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? The Global. NET application. This file contains code that is executed in response to application-level and session-level events raised by ASP.

These events and objects declared in the Global. Note 1: The Global. Use it only when there is a need for it. Note 2: If a user requests the Global. External users cannot view the file. How to create Global. Adding a Global. Examining the methods related to the events in Global. 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.

You can specify your own authentication logic over here. You can use this method to give authorization rights to user. Methods corresponding to events that do not fire on each request.

Show me an example!! Let us see an example of how to use the Global. To catch unhandled errors, do the following. Add a Global. GetBaseException ;. ToString ;. End Sub.

In this article, we learnt that Global. 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. The History of ASP.

Was this article worth reading? Share it with fellow developers too. Feedback - Leave us some adulation, criticism and everything in between! As we know that it is called when the session for new user is created. PostBack is the name given to the process of submitting an ASP. NET page to the server for processing. PostBack is done if certain credentials of the page are to be checked against some sources such as verification of username and password using database.

Occurs when ASP. NET acquires the current state for example, session state that is associated with the current request. Occurs when a security module has established the identity of the user. NET server control is a tag written in a Web page to represent a programmable server -side object used for displaying a user interface element in a Web page.

NET server controls are tags that can be understood by the server. NET Cookie. NET Cookie is a small bit of text that is used to store user-specific information. When a user requests for a web page, web server sends not just a page, but also a cookie containing the date and time. This cookie stores in a folder on the user's hard disk.

Master pages allow you to create a consistent look and behavior for all the pages or group of pages in your web application. A master page provides a template for other pages , with shared layout and functionality. The master page defines placeholders for the content, which can be overridden by content pages.

NET manages four types of states : View State. Control State. NET Session. In ASP. NET session is a state that is used to store and retrieve values of a user. It helps to identify requests from the same browser during a time period session. It is used to store value for the particular time session. The truth is that each request has its own instance of the HttpApplication class. To be more specific, the ASP.

NET runtime keeps two pools of HttpApplication objects. Which class is then responsible for managing those pools? Here is where the HttpApplicationFactory comes into play. There is only one instance of this class per HttpRuntime and besides managing app pools, it is also responsible for compiling Global. We will use System. Trace so some changes to the web. After the first client request, your webapp. Now look at the TestMessage property value — it was set only for the HttpApplication instance that was created as the first one.

You can stop reading here if what I wrote is satisfactory for you. If you still have some doubts and would like to dig deeper, keep on reading : — I will show you how to look at the ASP. Basically, you start with attaching to the w3wp. NET 2. Then dump its content — I highlighted the special and normal application pools which are actually of type System. Stack :. To find out which HttpApplication instances are stored in the particular pool, you need to dump the pool and then its internal array content:.

To check that this instance is the one that we got in the log file, we need to look through its properties and compare, for example, the GUID value:. I hope that this post helped you better understand the Global. NET applications. A simple web project is available for download here. Sign in Email. Forgot your password? Search within: Articles Quick Answers Messages.