Scribd
Upload
38 views

General Page Life-Cycle Stages

The ASP.NET page lifecycle involves a series of processing steps as a page runs. These include initializing controls, restoring and maintaining state, running event handlers, and rendering output. Understanding the page lifecycle is important for writing code at the appropriate stage and correctly initializing custom controls based on the page lifecycle events. The general stages are start, initialization, load, validation, postback event handling, rendering, and unload.

Uploaded by

Sadaf Ahmad
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
38 views

General Page Life-Cycle Stages

The ASP.NET page lifecycle involves a series of processing steps as a page runs. These include initializing controls, restoring and maintaining state, running event handlers, and rendering output. Understanding the page lifecycle is important for writing code at the appropriate stage and correctly initializing custom controls based on the page lifecycle events. The general stages are start, initialization, load, validation, postback event handling, rendering, and unload.

Uploaded by

Sadaf Ahmad
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Asp.

net page life cycle


When an ASP.NET page runs, the page goes through a life cycle in which it performs a series of processing steps. These include initialization, instantiating controls, restoring and maintaining state, running event handler code, and rendering. It is important for you to understand the page life cycle so that you can write code at the appropriate life-cycle stage for the effect you intend. Additionally, if you develop custom controls, you must be familiar with the page life cycle in order to correctly initialize controls, populate control properties with view-state data, and run any control behavior code. (The life cycle of a control is based on the page life cycle, but the page raises more events for a control than are available for an ASP.NET page alone.)

General Page Life-cycle Stages


In general terms, the page goes through the stages outlined in the following table. In addition to the page life-cycle stages, there are application stages that occur before and after a request but are not specific to a page. For more information, see ASP.NET Application Life Cycle Overview. Stage Page request Description The page request occurs before the page life cycle begins. When the page is requested by a user, ASP.NET determines whether the page needs to be parsed and compiled (therefore beginning the life of a page), or whether a cached version of the page can be sent in response without running the page. In the start step, page properties such as Request and Response are set. At this stage, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. Additionally, during the start step, the page's UICulture property is set. During page initialization, controls on the page are available and each control's UniqueID property is set. Any themes are also applied to the page. If the current request is a postback, the postback data has not yet been loaded and control property values have not been restored to the values from view state. During load, if the current request is a postback, control properties are loaded with information recovered from view state and control state. During validation, the Validate method of all validator controls is called, which sets the IsValid property of individual validator controls and of the page.

Start

Page initialization Load Validation

Postback event If the request is a postback, any event handlers are called. handling Before rendering, view state is saved for the page and all controls. During the rendering phase, the page calls the Render method for each control, providing a Rendering text writer that writes its output to the OutputStream of the page's Response property.

Unload

Unload is called after the page has been fully rendered, sent to the client, and is ready to be discarded. At this point, page properties such as Response and Request are unloaded and any cleanup is performed.

You might also like