You can just disable viewstate on the page. No need for each control. But it will not work in ur case. You are going to need viewstate enabled for submitting your form if the page is posting back to itself otherwise the form values will get reset on post back and ur code will grad the default values.
Only way to disable viewstate would be to have the form action set to post to another page.
I see, so if a user enters information that is invalid, the only way to re-display the form, using their values, and showing the validator text, viewstate needs to be implemented?
Here's a question then, is it possible to set the values myself after initializing the controls, using values from Page.Form() instead? The reason is that the pages won't be displayed again if successfull. Instead, they redirect one level back. I.E. options/create.aspx will redirect back to options/manager.aspx to display the master list of options.
You can set the control values before the page load event fires (is page_init) and viewstste will not be tracked. It helps greatly to fully understand the page lifecycle and how viewstate truely works.
Just a quick followup question on this. On a relatively simple page, with ViewState on all the runat="server" controls (including <head>) as well as the @Page directive, turned OFF, is it sill normal to see the following in a rendered page? It seems pretty nominal, I just wanted to be sure I wasn't missing a setting somewhere.