ansaurus

Question

Answer 1

+4 A:

ViewState can grow ugly on you. Basically I would say that the problem is that ViewState is enabled by default on everything, and a lot of things don't need it to be. The most basic example would be Label objects.

Try disabling ViewState where you find it unnecessary (EnableViewState is the property you're looking for).

Marpe 2009-07-31 07:29:14

Would it depend on objects per page or in the entire application?

Jaelebi 2009-07-31 07:32:26

It would depend on the objects in that page.

SharePoint Newbie 2009-07-31 07:46:17

Might be worth adding an example: `<asp:Label ID="productName" EnableViewState="false" Text="[Product Name]" runat="server" />`

Blixt 2009-07-31 07:47:59

Answer 2

+3 A:

Look into enabling Asp.Net tracing (http://www.asp101.com/articles/robert/tracing/default.asp) for your web pages - that will tell you what controls are storing how much in viewstate. You can then go and disable viewstare for controls that you know aren't using it.

Kragen 2009-07-31 07:50:01

Thanks for the tip. The problem was a dropdown list that was populated from a database. Dont know why it had a huge viewstate.

Jaelebi 2009-07-31 08:12:46

I recommend the approach of programming without viewstate; enable and use only if required by the form and/or controls. In this case you might want to evaluate if viewstate is necessary for this particular control. If not sure, disable it at the control level, see what breaks, then re-enable it. Viewstate size may be multiples of the control's actual data size, so you should populate data sparingly - only include what's needed.

Matt 2009-08-01 23:26:37

ansaurus

tags:

views:

answers:

Large ViewState value in ASP.NET

related questions