What I learnt today: January 2013

Hello friends,

I know this information is easily available over the net. However I just thought to share it on my blog just for quick reference. Here I have written ASP.Net page life cycle events in an order of there execution with one liner explanation.
public partial class Home : System.Web.UI.Page
    {
        protected void Page_PreInit(object sender, EventArgs e)
        {
            //Initialize themes, master page, profile properties
            //check IsPostBack, cross-page postbacks
            System.Diagnostics.Trace.WriteLine("Inside Page_PreInit");
        }

        protected void Page_Init(object sender, EventArgs e)
        {
            //Initialize or read control properties here
            System.Diagnostics.Trace.WriteLine("Inside Page_Init");
        }

        protected void Page_InitComplete(object sender, EventArgs e)
        {
            // Changes to ViewState that you want in next postback
            System.Diagnostics.Trace.WriteLine("Inside Page_InitComplete");
        }

        protected void Page_PreLoad(object sender, EventArgs e)
        {
            //Raised when page loads ViewState for itself and controls
            System.Diagnostics.Trace.WriteLine("Inside Page_PreLoad");
        }

        protected void Page_Load(object sender, EventArgs e)
        {
            //Set control properties, initiate Database connections
            System.Diagnostics.Trace.WriteLine("Inside Page_Load");
        }

        protected void Page_LoadComplete(object sender, EventArgs e)
        {
            //tasks that require that all other controls on the page be loaded.
            System.Diagnostics.Trace.WriteLine("Inside Page_LoadComplete");
        }

        protected void Page_Prerender(object sender, EventArgs e)
        {
            //to make final changes to the contents of the page or its
            //controls before the rendering stage begins
            System.Diagnostics.Trace.WriteLine("Inside Page_Prerender");
        }
        protected void Page_PrerenderComplete(object sender, EventArgs e)
        {
            //Raised after each data bound control whose 
            //DataSourceID property is set calls its DataBind method.
            System.Diagnostics.Trace.WriteLine("Inside Page_PrerenderComplete");
        }
        protected void Page_SaveStateComplete(object sender, EventArgs e)
        {
            //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
            System.Diagnostics.Trace.WriteLine("Inside Page_SaveStateComplete");
        }
        protected void Page_Render(object sender, EventArgs e)
        {
            //This is not an event; instead, at this stage of processing, the Page object calls this method on each control
            System.Diagnostics.Trace.WriteLine("Inside Page_Render");
        }
        protected void Page_Unload(object sender, EventArgs e)
        {
            //Raised for each control and then for the page.
            //During the unload stage, the page and its controls have been rendered, so you cannot make further changes to the response stream. 
            //If you attempt to call a method such as the Response.Write method, the page will throw an exception.
            System.Diagnostics.Trace.WriteLine("Inside Page_Unload");
            //Response.Write("This is not allowed");
        }
    }
What I learnt today

ASP.Net Page Life Cycle

Labels

Pages
