M
Moe
I'm experimenting with different ways of handling state.
ViewState is definitely cool. But I want to see how
things work without it. So, I'm trying to disable
ViewState.
When I use the Web Forms designer to set "enableViewState"
to "False", it is correctly reflected in the .aspx code
for my page. But when I run the app, state values in my
form still persist between round-trips. And when I do
View-->Source in the browser, I see that the rendered HTML
code still has the hidden VIEWSOURCE information in it.
I've also tried setting EnableViewState to false on
individual controls. The result is similar: .aspx code
says enableViewState="False" but viewstate is still
rendered...and the behavior is still consistent with
persisted state values on the page.
What do I need to do REALLY disable view state?
Thanks in advance.
ViewState is definitely cool. But I want to see how
things work without it. So, I'm trying to disable
ViewState.
When I use the Web Forms designer to set "enableViewState"
to "False", it is correctly reflected in the .aspx code
for my page. But when I run the app, state values in my
form still persist between round-trips. And when I do
View-->Source in the browser, I see that the rendered HTML
code still has the hidden VIEWSOURCE information in it.
I've also tried setting EnableViewState to false on
individual controls. The result is similar: .aspx code
says enableViewState="False" but viewstate is still
rendered...and the behavior is still consistent with
persisted state values on the page.
What do I need to do REALLY disable view state?
Thanks in advance.