Which of the following statements is true about the control state client-based technique?
A.
It is not versatile, as custom adapters cannot be written to control the manner of storing control
state data.
B.
It is not reliable to manage the state of controls, as it is not available if the view state is disabled at
the page level.
C.
Unlike the view state, it cannot be disabled.
D.
It does not require any server resources, as it is stored in hidden fields on a Web page.
Explanation:
Control state is like View state but functionally independent. Control state retains control property
information during multiple round trips to the server. The control state data is specific to a custom
control and is retained even if the View state is disabled at the page level. Control state cannot be
disabled and it is designed for storing a control’s necessary data that must be available on postback
to enable the control to function even when View state has been disabled. By default, the ASP.NET
page framework stores Control state in the page in the same hidden element in which it stores View
state. Use Control state only for small amounts of critical data that are necessary for the control
across postbacks. Do not use control state as a substitute to View state. The following are the
advantages of using control state client-based technique:
It does not require any server resources, as it is stored in hidden fields on a Web page.
It is more reliable to manage the state of controls, as it is available even if the view state is disable at
the page level. It is more versatile, as custom adapters can be written to control the manner of
storing control state data.