Answer Posted / dipal bhavsar
1. OnInit (Init) Initializes each child control of the current
2. LoadControlState: Loads the ControlState of the control.
To use this
method the control must call the
Page.RegisterRequiresControlState method in
the OnInit method of the control.
3. LoadViewState: Loads the ViewState of the control.
4. LoadPostData: Is defined on interface
IPostBackDataHandler. Controls that
implement this interface use this method to retrieve the
incoming form data and
update the control s properties accordingly.
5. Load (OnLoad): Allows actions that are common to every
request to be
placed here. Note that the control is stable at this time;
it has been
initialized and its state has been reconstructed.
6. RaisePostDataChangedEvent: Is defined on the interface
IPostBackData-Handler.
Controls that implement this interface use this event to
raise change events in
response to the Postback data changing between the current
Postback and the
previous Postback. For example if a TextBox has a
TextChanged event and
AutoPostback is turned off clicking a button causes the
Text-Changed event to
execute in this stage before handling the click event of the
button which is
raised in the next stage.
7. RaisePostbackEvent: Handles the client-side event that
caused the Postback
to occur
8. PreRender (OnPreRender): Allows last-minute changes to
the control. This
event takes place after all regular Post-back events have
taken place. This
event takes place before saving ViewState so any changes
made here are saved.
9. SaveControlState: Saves the current control state to
ViewState. After this
stage any changes to the control state are lost. To use this
method the
control must call the Page.RegisterRequiresControlState
method in the OnInit
method of the control.
10. SaveViewState: Saves the current data state of the
control to ViewState.
After this stage any changes to the control data are lost.
11. Render: Generates the client-side HTML Dynamic Hypertext
Markup Language
(DHTML) and script that are necessary to properly display
this control at the
browser. In this stage any changes to the control are not
persisted into
ViewState.
12. Dispose: Accepts cleanup code. Releases any unman-aged
resources in this
stage. Unmanaged resources are resources that are not
handled by the .NET common
language runtime such as file handles and database connections.
13. UnLoad
| Is This Answer Correct ? | 2 Yes | 3 No |
Post New Answer View All Answers
Can you change a master page dynamically at runtime? How?
What is viewstate? What does the "enableviewstate” property do? Whay would I want it on or off?
Explain what benefit does your code receive if you decorate it with attributes demanding specific security permissions?
What are Master Pages in ASP.NET?
What is the recommended approach for asp.net mvc to globally intercept exceptions? What other functionality can be implemented with the approach? : Asp.Net MVC
Explain a program using code nuggets to create a simple application? : asp.net mvc
How do you identify that the page is postback?
List the asp.net validation controls?
Explain the features that make asp.net more used framework? : asp.net mvc
Explain the boxing and unboxing concept in .net?
How can we register exception filter from the action?
What are the advantages of Web API?
Difference between overriding and overloading?
What is parse in asp.net?
Which method do you use to kill explicitly a users session?