Completely remove ViewState for specific pages

Question

I have a site that features some pages which do not require any post-back functionality. They simply display static HTML and don't even have any associated code. However, since the Master Page has a <form runat="server"> tag which wraps all ContentPlaceHolders, the resulting HTML always contains the ViewState field, i.e:

<input
  type="hidden"
  id="__VIEWSTATE"
  value="/wEPDwUKMjEwNDQyMTMxM2Rk0XhpfvawD3g+fsmZqmeRoPnb9kI="
/>

EDIT: I tried both variants of setting EnableViewState on page level with no luck at all:

<%@ Page Language="C#" EnableViewState="false" %>
<%@ Page Language="C#" EnableViewState="true" %>

I realize, that when decrypted, this value of the input field corresponds to the <form> tag which I cannot remove because it is on my master page. However, I would still like to remove the ViewState field for pages that only display static HTML. Is it possible?

Rename your static file to .html or set EnableViewState to false in the page directive. — Mikael Svenson, Mar 12 '10 at 13:25

score 24 · Accepted Answer · edited Apr 17 '14 at 14:04

You could override Render and strip it out with a Regex.

Sample as requested. (NB: Overhead of doing this would almost certainly be greater than any possible benefit though!)

[edit: this function was also useful for stripping all hidden input boxes for using the HTML output as a word doc by changing the MIMEType and file extension]

protected override void Render(HtmlTextWriter output)
{
    StringWriter stringWriter = new StringWriter();

    HtmlTextWriter textWriter = new HtmlTextWriter(stringWriter);
    base.Render(textWriter);

    textWriter.Close();

    string strOutput = stringWriter.GetStringBuilder().ToString();

    strOutput = Regex.Replace(strOutput, "<input[^>]*id=\"__VIEWSTATE\"[^>]*>", "", RegexOptions.Singleline);

    output.Write(strOutput);
}

The NB should be written in bold, 20pt all caps instead of between parentheses. This is one of the top results in Google and people **will** use this code even though they shouldn't. I guarantee it. — Steven Liekens, Jun 29 '16 at 10:58

score 20 · Answer 2 · answered May 03 '11 at 01:03

Add following methods to the page:

        protected override void SavePageStateToPersistenceMedium(object state)
    {
        //base.SavePageStateToPersistenceMedium(state);
    }

    protected override object LoadPageStateFromPersistenceMedium()
    {
        return null; //return base.LoadPageStateFromPersistenceMedium();
    }

    protected override object SaveViewState()
    {
        return null;// base.SaveViewState();
    }

Result :

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="" />

@Craig : you are welcome, but I have moved away from asp pages and mvc, I prefer Angularjs and webservices instead so that many workarounds in asp.net are not needed. — jimjim, Sep 25 '13 at 01:04

score 4 · Answer 3 · answered Mar 12 '10 at 13:26

4

In the <% @page... directive at the top of the page, add EnableViewState="False". That will prevent the ViewState for that particular page.

answered Mar 12 '10 at 13:26

Jamie Chapman

4,229
5
29
47

2

This is already the case. However, the field is still there. I updated the question – Kerido Mar 12 '10 at 13:42

score 3 · Answer 4 · answered Mar 20 '11 at 23:18

The method suggested by Martin must be used very carefully; because it may cause unexpected behaviors in your pages as Martin pointed in parenthesis. I've actually experienced it. But there is another option to remove viewstate content from page safely.

This option gives you the ability to use viewstate without setting false, it also allows you to remove it from your pages. Please check the articles below:

1- http://www.eggheadcafe.com/articles/20040613.asp

2- http://aspalliance.com/72

There is a solution file zipped under the Peter's article [1] you can download. I recommend that you read the second article also referenced by Peter. This is a perfect solution to remove viewstate content from your page while using its capabilities.

score 2 · Answer 5 · edited May 23 '17 at 12:10

2

There will always be a ViewState. See this related question:

Why does __VIEWSTATE hidden field gets rendered even when I have the EnableViewState set to false

edited May 23 '17 at 12:10

Community

1
1

answered Jul 30 '10 at 14:41

Sean Moubry

1,010
1
13
22

1

According to my answer ViewState can have an empty value. – jimjim May 03 '11 at 01:19

score 1 · Answer 6 · edited Sep 03 '14 at 14:11

1

in .net4 you can just remove the runat="server" from the form tag. But you can't use server controls inside the form tag once you remove it.

edited Sep 03 '14 at 14:11

Mark

2,380
11
29
49

answered Sep 03 '14 at 13:06

Susantha

19
3

score 0 · Answer 7 · answered Dec 13 '13 at 17:36

0

ViewState is added only if an asp:Form is present in the page. Remove the Form, and the hidden field will not be rendered.

Beware: By doing this, you are also renouncing to have server-side event handlers, or any kind of PostBack events.

answered Dec 13 '13 at 17:36

jcarrenog

199
1
3

score 0 · Answer 8 · answered Jun 12 '14 at 10:00

0

Or just use a simple jQuery line to remove the fields, if you're using AJAX-style postback requests...

$(".aspNetHidden").remove();

This removes the DIV encasing the hidden __VIEWSTATE fields.

answered Jun 12 '14 at 10:00

andym0908

151
1
1
6

Simple and efficient: $(document).ready(function () { setTimeout(function () { $("#__VIEWSTATE").remove(); $("#__VIEWSTATEGENERATOR").remove(); }, 300); }); – Khurram Ishaque Apr 04 '17 at 14:04

Completely remove ViewState for specific pages

8 Answers8

Linked