Thread: Disable ViewState

How would I disable ViewState (EnableViewState="false") on one specific xml.config file that displays a large list of manufacturers?
Or edit the page directive.

I tried:

Code:

<xsl:value-of select="&lt;%@ Page EnableViewState='False' %&gt;"
disable-output-escaping="yes" />

but that doesn't work...


Thx, _Brian

I could stand to be corrected, but here's my understanding of this:

XmlPackages aren't parsed/executed until after the requested ASP.net page has already processed page directives. So writing out a page directive from an XMLPackage is too late to make any effect in this page requests lifecycle. (You might even the output in the source of the page returned to the clients browsers, try it to prove our hypothesis here.)

But I understand what you need. I found this post while thinking along the same lines myself. For certain pages I imagine you could potentially disable the ViewState within the page rendering engine like "ShowCategory.aspx", but I haven't checked what else is in the viewstate.

Maybe one of the ASPDNSF staff could comment on what else might be lost by disabling ViewState on certain pages that don't normally post-back?

I disabled the ViewState (EnableViewState="false") on the
searchadv.aspx and showmanufacturers.aspx pages.

That worked for me. Now did disabling the ViewState actually speed the page up?

That's the real question...

Thx, _Brian

It may not have spead up your page rendering time (cpu processing on the server); but it will for sure have saved you and your visitors unnecessary bandwidth which costs money and time.

You might not notice this on a small site (where your server never reaches 100% load), but for those of us on shared servers or with high traffic the change would be noticeable.

Its kind of like taking extra junk out of your car trunk becuase it will save you some gas. Your car was never broken before, but you were paying to drive around with extra weight on board. Why pay to carry this around if it serves no purpose?
- Ben