If you link to the page life cycle, you can find an overview here .
Life Cycle Summary:
Page request
A page request occurs before the start of the page life cycle. When a page is requested by the user, ASP.NET determines whether the page should be parsed and compiled (therefore, the page will begin to serve), or whether it is possible to send a cached version of the page in response without starting the page.
Start
Initially, page properties are set, such as request and response. At this point, the page also determines whether the request is a postback or a new request and sets the IsPostBack property. In addition, the UICulture property of the page is initially set.
Page initialization
During page initialization, the controls on the page are available and each UniqueID control is installed. Any themes also apply to the page. If the current request is postback, postback data has not yet been loaded, and control property values ββhave not been restored to values ββfrom the view state.
Load
At boot time, if the current request is reverse processing, control properties are loaded with information recovered from the view state and control state.
Validation
During validation, the Validate method of all validation controls is called, which sets the IsValid property for individual validation elements and the page.
Handling Inverse Events
If the request is a postback, all event handlers are called.
Rendering
Before rendering, the 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 text script that writes its output to the Response property's OutputStream.
Unload
Unloading is called after the page has been fully displayed, sent to the client and ready to be discarded. At this point, page properties, such as Response and Request, are unloaded and any cleanup is performed.
As for the GridView events, they can be found here .