ASP.NET is a web development platform, which gives a programming version, a complete software program infrastructure, and various offerings required to build up robust internet packages for computers, as well as cell gadgets.

ASP.NET works on the pinnacle of the HTTP protocol and makes use of the HTTP commands and guidelines to set a browser-to-server bilateral communique and cooperation.

Asp.Net is part of the Microsoft .Net platform. Asp.Net packages are compiled codes, written the usage of the extensible and reusable components or gadgets present within the .NET framework. Those codes can use the whole hierarchy of classes in the .NET framework.

ASP.NET is a software program framework that enables the fast development of software programs of any type by using presenting reusable additives. It may be mounted on computers running Microsoft home windows running systems. There are primary components of the asp.Net framework, one is CLR (Common Language Runtime) and FCL (Framework base Class Library). The CLR is used to locate, load, and manage .Net kinds. The CLR additionally takes care of several low-stage information including reminiscence management, threads, item context barriers, and exception dealing with. On this subject matter, we're going to learn about the ASP.NET lifestyles cycle.

We can divide the asp.net lifecycle into application lifecycle and page life cycle. Let’s discuss this one by one.

Asp.net life cycle of the application is as follows

The user first requests a page on the website.

The request is routed to the processing pipeline, which forwards it to the asp.net runtime.

net runtime creates an instance of the ApplicationManager class. The ApplicationManager instance represents the .net framework domain that will be used to execute the request for your application. An appellation domain isolates global variables from other applications and allows each application to load and unload separately as required.

After the application domain has been created an instance of the Hosting environment class is created. This class provides access to items inside the hosting environment, such as directory folders.

net creates an instance of the core object that will be used to process the request. This includes HttpContext, HttpRequest, and HTtpResponse objects.

net creates an instance of the HttpApplication class. this class is also the base class for the site’s global.asax file. This class is used to trap events that happen when your application starts or stops. When asp.net creates an instance of HttpApplication, it also creates the modules configured for the application such as SessionStateModule.

Finally, asp.net processes request through the HttpApplication pipeline. This pipeline also includes a see of events for validating requests, mapping URLs, accessing the cache, and more. These events are of interest to developers who want to extend the application class.

HttpApplication class provides several events you can handle to perform actions when asp.net raises certain events on the application level, the events won’t work on the pre-user level.  following are the most common events used by developers.

Application_Start: It is raised when your application is started by IIS.

Application_End: It is raised when the tour application stops or shuts down.

Application_Error: It is raised when an unhandled error occurs and rises to the application scope.

Application_LogRequest: It is raised when a request has been made to the application.

Application_PostLogRequest: It is raised after the logging of the request has been completed.

Apart from the application life cycle, there is also the page life cycle for each page on the website.

On the webserver, asp net compiles the page or pulls from the cache.

Start: Set request and response objects. Determine IsPostBack.

Init: Initialized Page controls but not their properties. Apply page theme.

Load: If PostBack, load control properties from view State.

Validation: Validate page and validator controls.

Call control even handlers for PostBack requests.

Rendering: Save view state. Render control and display the page.

Unload: unload request and response objects. Perform clean-up. The page is ready to be discarded. Return response to the user.

Following are the most common events used by developers

Int: It is raised after each control has been initialized

print: This event is used only if you need to set the values such as the master page or theme.

incomplete: It is raised after all initialization of the page and its controls have been completed.

PreLoad: It is raised before the view state has been loaded for the page and its controls and before postback processing.

Load: Page load event is called first. Then the load event for each child control is called in turn.

Control events: Asp.net calls any event on the page or its controls that caused the postback to occur. This might be a button click event or drop-down list.

LoadComplete: At this point, all control are loaded. If you need to do additional processing at this time, you can do so here.

PreRender: It allows final changes to the page r its control. It takes place after all regular postback events have taken place.

SaveStateComplete: It is useful if you need to write processing that requires the view state to be set.

Render: asp.net calls this method on each of the page’s controls to get its output.

Unload: This event is used for clean-up code. we can use it to manually release resources, a process that is rarely necessary.

In this blog, we will discuss the ASP .NET life cycle.

ASP.NET life cycle

The levels of the asp.net page life cycle are initialization, instantiation of controls, restoration and renovation of the kingdom, execution of event handler codes, and page rendering. Asp.net web page lifestyles cycle is an internet software framework that becomes advanced and advertised via Microsoft to allow programmers to construct dynamic web packages. It permits customers to apply featured languages like c# or vb.net. It uses the HTTP instructions, works on a pinnacle of the HTTP protocol, and uses HTTP guidelines to set bilateral verbal exchange for browser-to-server. Asp.Net codes can be written in any of these languages: c#, j#, JScript, or visible primary.net. Asp.net has a massive wide variety of controls like text containers, buttons, and labels that may be required for manipulating and assembling the code for the advent of HTML pages.

The various stages of the ASP.NET Page Life Cycle are as below:

In this stage, the IsPostBack property is checked to find whether or not it is the first time that the page is being processed.

Creation or re-creation of dynamic controls.

Setting up the Theme property dynamically.

This stage fires up after each control has been initialized.

This stage is also used to initialize control properties.

The event is first of all fired for the bottom-most control and then fired upwards the hierarchy until the page itself.

This event can be used to make changes to the view state.

The event can be used for task processing that needs initialization to be completed.

This particular event is always raised after the state is displayed by page load for itself as well as all controls, as well as after it processes the postback data that has gone along with the Request instance.

OnPreLoad also loads view state for itself as well as all controls before the Page instance raises this particular event, and after that processes any postback data in the Request instance.

The load method is called on the Page object, and then recursively, it does the same for each child control all controls are loaded. The Load event of the page occurs before the Load event of the individual controls.

It is the first place in the page lifecycle where all values are restored.

The value of IsPostBack is checked mostly to avoid unnecessary resetting state.

We can call the validate method and verify that IsValid.

We can also create dynamic controls here.

OnLoad event method is also used to establish database connections and set properties in controls.

NET would now call those events on the page or either its controls that had caused the PostBack to take place.

In this event, if the page has any of the validator controls, we need to check the IsValid property of the Page before we perform any kind of processing, and also we need to check the same property for individual validation controls.

It is an example of a control event such as the button click event that has caused the postback.

This event is raised at the end of the event-handling stage.

LoadComplete event is used for the work that requires all remaining controls on the page to get loaded.

OnPreRender event will be raised only after the Page object has created all required controls as well as child controls to render the page.

PreRender event on the Page object is raised by Page Object, and afterward, recursively, it does the same for each of the children.

The PreRender event of the page occurs before the PreRender event of the individual controls.

It also allows final changes to the page.

This stage occurs before saving ViewState, so changes that are made here are saved.

This is raised after the view state as well as the control state have been saved for the page and controls.

ViewState has been saved for the page and all controls before this particular event occurs.

Any changes that are made to the page or controls at this stage would be ignored.

The render method is the method of the page object and its controls, and it is not an event.

This method generates the Dynamic Hypertext Markup Language (DHTML), client-side HTML, and also the scripts that are necessary to properly display control in the browser.

Here, all of the processing has occurred, and it is now safe to dispose of any remaining objects that include Page objects as well.

Unload event occurs for each control and then finally for the page.

During this stage, the page and its controls have been rendered, thus not making it possible to make further changes to the response stream.

If you call a method such as the Response. Then the page would throw an exception.

In this blog, we will discuss ASP.NET Page Life Cycle

life cycle

Trending Blogposts on life cycle

ASP.NET life cycle

ASP.NET Page Life Cycle

Popular Discussions on life cycle

PRODUCTS

QUICK LINKS

LEGAL

life cycle

Trending Blogposts on life cycle

ASP.NET life cycle

ASP.NET Page Life Cycle

Popular Discussions on life cycle