When a page is requested, it is loaded into the server memory, processed and sent to the browser. Then it is unloaded from the memory. At each of this steps, methods and events are available, which could be overridden according to the need of the application. In other words, you can write your own code to override the default code. The Page class creates a hierarchical tree of all the controls on the page. All the components on the page, except the directives are part of this control tree. You can see the control tree by adding trace= "true" to the Page directive. We will cover page directives and tracing under 'directives' and 'error handling'. The page life cycle phases are : Initialization Instantiation of the controls on the page Restoration and maintenance of the state Execution of the event handler codes Page rendering Understanding the page cycle helps in writing codes for making some specific thing happen at any stage of the page life cycle...