ASP.NET ViewState Interview Questions And Answers updated in 2019

What is ASP.NET ViewState?

The advantage of ASP.NET ViewState is lot of burden will be reduced on the developer and memory will not be reserved permanently on the client machine or server machine.

The disadvantage of ASP.NET ViewState is lot of transmission will be happen between browser and web server.

And you can find the complete State Management Techniques from my other post.

What are the different ways to apply ViewState in Asp.Net?

1. Control level
2. Page level
3. Application level

1. Control level
<input type=…. enableViewState =”true(default)/false”>
When there is a sensitive data it is strongly recommended to disable ViewState for the security reason, if it is password type text box by default ViewState will be disabled.

2. Page level
<%@ page…. enableViewState=”true(default)/false” %>
It will be applied for all the controls.

3. Application level
Need to add below element in web.config file.
<pages enableViewState=”true(default)/false” …>
It will be applied for all the pages.

How do you enable or disable a ViewState for a control on the page?

Every ASP.NET control has a property called EnableViewState. If EnableViewState is set to true ViewState is enabled for the control. If EnableViewState is set to false ViewState is disabled for the control.

How do you enable or disable a ViewState at the page level?

At the page level you can enable or disable ViewState using EnableViewState property of the page.

What is the name of the hidden form field in which ViewState of the page is saved?

__ViewState

What are the performance implications of ViewState?

ViewState is usually good to retain the state of the controls on the webform across postbacks. If you have a huge DataGrid with tons of data being loaded on every page load. It is a good idea to disable the ViewState of the DataGrid for the page to load faster. If the ViewState of a large DataGrid is not disabled, ViewState can easily get very large, on the order of tens of kilobytes. Not only does the __ViewState form field cause slower downloads, but, whenever the user posts back the Web page, the contents of this hidden form field must be posted back in the HTTP request, thereby lengthening the request time, as well.

When does ViewState restoration happens?

During the Page_Init event

What are the disadvantages of using ViewState?

1. On all page visits, during the save view state stage the Page class gathers the collective view state for all of the controls in its control hierarchy and serializes the state to a base-64 encoded string. (This is the string that is emitted in the hidden __ViewState form filed.) Similarly, on postbacks, the load view state stage needs to deserialize the persisted view state data, and update the pertinent controls in the control hierarchy.

2. The __ViewState hidden form field adds extra size to the Web page that the client must download. For some view state-heavy pages, this can be tens of kilobytes of data, which can require several extra seconds (or minutes!) for modem users to download. Also, when posting back, the __ViewState form field must be sent back to the Web server
in the HTTP POST headers, thereby increasing the postback request time.

Is ASP.NET ViewState encoded?

Yes, ViewState is base-64 encoded.

Can you encrypt ViewState of Page?

Yes, we can use the LosFormatter class to encrypt ViewState of Page

Can the HTML controls retian State accross postbacks?

No, by default HTML controls donot retain state accross postbacks.

Can you make HTML controls retain State accross postbacks?

Yes, HTML controls can retain State accross postbacks, if you convert HTML controls to Server Controls. There are 2 ways to convert HTML control to Server Controls.

1. Right click on the HTML Control and then click “Run As Server Control”
Or
2. Set runat=”server” attribute for the Control.

Is ViewState supported in classic ASP?

No,ViewState is introduced in asp.net, it was not in classic asp.

When a form is submitted in classic ASP, all form values are cleared. Suppose you have submitted a form with a lot of information and the server comes back with an error. You will have to go back to the form and correct the information. You click the back button, and what happens…….ALL form values are CLEARED, and you will have to start all over again! The site did not maintain your ViewState.

When a form is submitted in ASP .NET, the form reappears in the browser window together with all form values. How come? This is because ASP .NET maintains your ViewState. The ViewState indicates the status of the page when submitted to the server.

Is ViewState of one page available to another page?

No, ViewState of a Page is available only in that page. You cannot access ViewState of one page from another page.

Can you programatically store and retrieve data from ViewState?

Yes. In ASP.NET you can programatically store and retrieve data from ViewState.See the example below

//Save the value in ViewState object
ViewState(“SomeVar”) = txtFirstName.text;

//Retrieve the value from ViewState object
String strFirstName = ViewState(“SomeVar”).ToString();

Can someone view the Page HTML source and read ViewState?

No. ViewState is base-64 encoded. Hence you cannot read ViewState. If you right click on the Page and View Source you will find __ViewState is base-64 encoded.

What happens during the Page_Init event?

The server controls are loaded and initialized from the Web form’s view state. This is the first step in a Web form’s life cycle.