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. The following are the various stages or events of ASP.Net page life cycle.

Following are the different stages of an ASP.NET page life cycle:

PreInit:

Raised after the start stage is complete and before the initialization stage begins.

Use this event for the following:

 

o    Check the IsPostBack property to determine whether this is the first time the page is being processed. The IsCallbackand IsCrossPagePostBack properties have also been set at this time.

o    Create or re-create dynamic controls.

o    Set a master page dynamically.

 

protected void Page_PreInit(object sender, EventArgs e)
   {
           
   }

 

Init:

Raised after all controls have been initialized and any skin settings have been applied. The Init event of individual controls occurs before the Init event of the page.

Use this event to read or initialize control properties.


protected void Page_Init(object sender, EventArgs e)
        {
           
        }

InitComplete:

Raised at the end of the page's initialization stage. Only one operation takes place between the Init and InitComplete events: tracking of view state changes is turned on. View state tracking enables controls to persist any values that are programmatically added to the ViewState collection. Until view state tracking is turned on, any values added to view state are lost across postbacks. Controls typically turn on view state tracking immediately after they raise their Init event.

Use this event to make changes to view state that you want to make sure are persisted after the next postback.

 

 

 

protected void Page_InitComplete(object sender, EventArgs e)
        {
           
        }

PreLoad:

Raised after the page loads view state for itself and all controls, and after it processes postback data that is included with the Request instance.

protected override void OnPreLoad(EventArgs e)
        {
           
        }

Load:

The Page object calls the OnLoad method on the Page object, and then recursively does the same for each child control until the page and all controls are loaded. The Load event of individual controls occurs after the Load event of the page.

Use the OnLoad event method to set properties in controls and to establish database connections.

 

protected void Page_Load(object sender, EventArgs e)
        {
           
        }

 

LoadComplete:

Raised at the end of the event-handling stage.

Use this event for tasks that require that all other controls on the page be loaded.

 

  protected void Page_LoadComplete(object sender, EventArgs e)
        {
          
        }

PreRender:

Raised after the Page object has created all controls that are required in order to render the page, including child controls of composite controls. (To do this, the Page object calls EnsureChildControls for each control and for the page.)

The Page object raises the PreRender event on the Page object, and then recursively does the same for each child control. The PreRender event of individual controls occurs after the PreRender event of the page.

Use the event to make final changes to the contents of the page or its controls before the rendering stage begins.


  protected override void OnPreRender(EventArgs e)
        {
            
        }

PreRenderComplete:

Raised after each data bound control whose DataSourceID property is set calls its DataBind method. For more information, see Data Binding Events for Data-Bound Controls later in this topic.

SaveStateComplete:

Raised after view state and control state have been saved for the page and for all controls. Any changes to the page or controls at this point affect rendering, but the changes will not be retrieved on the next postback.

protected override void OnSaveStateComplete(EventArgs e)
        {
            
        }

Render:

This is not an event; instead, at this stage of processing, the Page object calls this method on each control. All ASP.NET Web server controls have a Render method that writes out the control's markup to send to the browser.

If you create a custom control, you typically override this method to output the control's markup. However, if your custom control incorporates only standard ASP.NET Web server controls and no custom markup, you do not need to override the Render method. For more information, see Developing Custom ASP.NET Server Controls.

A user control (an .ascx file) automatically incorporates rendering, so you do not need to explicitly render the control in code.

 

Unload:

Raised for each control and then for the page.

In controls, use this event to do final cleanup for specific controls, such as closing control-specific database connections.

For the page itself, use this event to do final cleanup work, such as closing open files and database connections, or finishing up logging or other request-specific tasks.

 

protected void Page_UnLoad(object sender, EventArgs e)
        {
            
        }  


I hope this will help to you.

0 comments


Leave a comment

Make sure you enter the (*) required information where indicated. HTML code is not allowed.

You may also like