What is the advantage of using control state instead of view state when I create a custom control in ASP.NET?
Why use control state?
Does a good article about this exist?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the advantage of using control state instead of view state when I create a custom control in ASP.NET?
Why use control state?
Does a good article about this exist?
The difference between ViewState and ControlState is that ViewState can be disabled by the developer, whereas ControlState cannot be disabled.
Therefore, when developing custom controls, when to use ViewState or ControlState ?
Typically, if the persistence of the data can be viewed as a feature, use ViewState. For example, in some scenarios, it is convenient when a DropDownList saves all its items in ViewState, and in other scenarios it is preferable to just rebind the control (and keep the page size and amount of data to post low).