P
Philip Tripp
I've read numerous sources stating that view state can be disabled per
control, and per page, but can't seem to keep web form controls from
remembering their state on a postback. I'm using VS.Net 2002, .Net
Framework 1.0 SP2.
I create a new project, and add a new web form to the project. On the
page properties, I set EnableViewState to False and verify that the @
Page directive has "enableViewState=false" in it. I then add a TextBox
control from the Web Froms, and set its EnableViewState property to
false. I add a Button control from the Web Forms, and start my project
(F5). I type in some text to the textbox, click the button so the form
submits, and expect that the text box come back empty (because view
state has been disabled), but it always comes back populated.
I am new to ASP.NET, so am I somehow misunderstanding the dozen or so
aricles I've read about view state? Is view state always remembered on
post backs? If it is always remembered, then what the heck does setting
EnableViewState to false do?
control, and per page, but can't seem to keep web form controls from
remembering their state on a postback. I'm using VS.Net 2002, .Net
Framework 1.0 SP2.
I create a new project, and add a new web form to the project. On the
page properties, I set EnableViewState to False and verify that the @
Page directive has "enableViewState=false" in it. I then add a TextBox
control from the Web Froms, and set its EnableViewState property to
false. I add a Button control from the Web Forms, and start my project
(F5). I type in some text to the textbox, click the button so the form
submits, and expect that the text box come back empty (because view
state has been disabled), but it always comes back populated.
I am new to ASP.NET, so am I somehow misunderstanding the dozen or so
aricles I've read about view state? Is view state always remembered on
post backs? If it is always remembered, then what the heck does setting
EnableViewState to false do?