Skip to main content

ASP.NEt 2.0 Viewstate and good practices

View state is one of the most important features of ASP.NET because it enables stateful programming over a stateless protocol such as HTTP. Used without strict

criteria, though, the view state can easily become a burden for pages. Since view state is packed with the page, it increases size of HTTP response and request.

Fortunately the overall size of the __VIEWSTATE hidden field (in ASP.NET 2.0) in most cases is as small as half the size of the corresponding field in ASP.NET 1.x.The content of the _VIEWSTATE field (in client side) represent the state of the page when it was last processed on the server. Although sent to the client, the view state doesn't

contain any information that should be consumed by the client.

In ASP.NET 1.x, if you disable view state of controls, some of them are unable to raise events hence control become unusable. When we bind data to a grid, server encodes and put whole grid in to view state, which will increase size of view state (proportional to the data volume of grid). We cannot disable view state, if we need features like pagination, edit, and sorting.

But in ASP.NET 2.0 view state can be disabled more freely. Because controls keep contents required for their behavior in control state. View state is purely to maintain control’s UI content. Following simple guidelines can be used to handle view state appropriately.

* Use page’s view state when data elements are required to persist between requests. E.g. ViewState("DataElement") = someDataElement

You can disable page view state by setting EnableViewState="false" in page directive of aspx.

* Do not use page’s view state to persist control’s data. Enable control’s view state, so data will be available between requests. E.g. data source of a Dropdown list

* If you populate the contents of a control (from some data source) every time a page is requested, it is generally safe (and wise) to disable view state for that control. E.g. EnableViewState="false"

(CheckBoxList, ContentPager, DetailsView, FormView, GridView, ListControl - base class for BulletedList, CheckBoxList, DropDownList, ListBox, and RadioButtonList, LoginView,

MultiView, Table, etc.. keep control state, hence view state can be disabled without affecting events.)

* If you don’t want to populate contents, you can declaratively place a data source on your page and point your control to that data source with view state enabled. Above controls exhibit intelligent use

of view state when bound to declarative data sources. So there wont be any hit to backend data source in post backs.

As a refactoring tip, disable view state at page level and check when and where it breaks. If functionality breaks, verify that you have used page view state correctly.

If you have used it properly, enable view state at page level and disable at each and every control level by considering above best practices

Comments

Post a Comment

Popular posts from this blog

Hosting WCF services on IIS or Windows Services?

There came one of those questions from the client whether to use II7 hosting or windows service hosting for WCF services. I tried recollecting a few points and thought of writing it down. WCF applications can be hosted in 2 main ways - In a Windows service - On IIS 7 and above When WCF was first released, IIS 6 did not support hosting WCF applications that support Non-HTTP communication like Net.TCP or Net.MSMQ and developers had to rely on hosting these services on Windows Services. With the release of IIS 7, it was possible to deploy these Non-Http based applications also on IIS 7. Following are the benefits of using IIS 7 to host WCF applications Less development effort Hosting on Windows service, mandates the creating of a Windows service installer project on windows service and writing code to instantiate the service, whereas the service could just be hosted on IIS by creating an application on IIS, no further development is needed, just the service implementa...
4 comments
Read more

Finalization, Know What it Costs

This is a post about object finalization in .NET. Finalization is not as inexpensive as we think, it increases the pressure put on GC.All objects that need finalization are moved into a finalizable queue and the actual finalization happens in a separate thread. Because the objects full state may be needed, the object itself and all the object it points to are promoted to the next generation (this is needed so that GC does not clean these objects off in the current round), and these objects are cleaned up only after the following GC. Due to this reason, resources that need to be released should be wrapped in as small a finalizable object as possible, for instance if your class needs a reference to an unmanaged resource, then you should wrap the unmanaged resource in a separate finalizable class and make that a member of your class and furthermore the parent should be a non-finalizable class. This approach will assure that only the wrapped class (class that contains the unmanaged resourc...
1 comment
Read more

The maximum nametable character count quota (16384) has been exceeded

Some of our services were growing and the other day it hit the quote, I could not update the service references, nor was I able to run the WCFTest client. An error is diplayed saying " The maximum nametable character count quota (16384) has been exceeded " The problem was with the mex endpoint, where the XML that was sent was too much for the client to handle, this can be fixed by do the following. Just paste the lines below within the configuration section of the devenve.exe.config and the svcutil.exe.config files found at the locations C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE , C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin Restart IIS and you are done. The detailed error that you get is the following : Error: Cannot obtain Metadata from net.tcp://localhost:8731/ Services/SecurityManager/mex If this is a Windows (R) Communication Foundation service to which you have access, please check that you have enabled metadata publishing at the specified address. F...
5 comments
Read more