viewstate

Is there any way I can simulate a proxy server truncating a viewstate? I avoid ViewState client-side entirely by putting it server-side. The code is about 5 lines long and I've seen a tremendous improvement in performance. http://aspadvice.com/blogs/robertb/archive/2005/11/16/13835.aspx You could fake a tampered viewstate easily using fiddler: http://www.fiddlertool.com/ How have you ascertained it is a proxy server? It doesn't sound likely that a proxy server would truncate parts of the HTML. However, if ViewState is interfered with then ASP.NET will throw an Invalid Viewstate exception. So,

<asp:TextBox ID="TextBox1" runat="server" EnableViewState="false" /> <asp:Button ID="Button1" runat="server" Text="Button" /> I have set the EnableViewState property to false, but when I click on the button the value in the textbox persists after the postback. Why does the value persist? Have a look at Understanding ASP.NET View State . In the page lifecycle, there is a Load Post Data stage that will populate your control values from the form data. View State can be very confusing, specifically why you need it if controls are populated with form data on post back. The Role of View State from

I am trying to make a strongly typed viewstate object. public class MyNewPage : ViewStatePage<MyNewPageViewStateStore> In the implementation of ViewStatePage, I am instantiating an object Store out of this.ViewState["_PageViewState"] . In the derived page, I'll be using that object and making changes to it. What's the last event called in an asp.net page that can still affect View State? Is it Unload ? In the ASP.net page lifecycle the order goes (this is the short version): Preinit -> Init -> Load Viewstate -> Page Load -> Events -> PreRender -> Save Viewstate -> Render -> Unload Places where

I have stumbled upon the issue when I need to retract html controls I've added client-side using JavaScript after the postback (due to server-side validation - this is not optional). Please tell me if the way I'm trying to achieve this is cr*p and there's a better way of doing this. basically, what I'm doing is cloning a textbox control for up to 10 times on the page when the user hits "Add" and storing entered values from each of those texboxes in a hidden field to read from in the code behind. This works fine, however, when the server side validation doesn't pass after postback, all those

I use 'n' number of server controls in my page. Now I am into performance tuning and I've noticed that my ViewState is too large and it makes my page slow. I know ViewState size can be compressed by Gzip. Any other suggestions for reducing ViewState in asp.net. I don't want to do in IIS because my web application is hosted on a shared server. Assuming the size of viewstate is the main cause of the 'slowness', I would like to suggestion you tackle it from a more holistic approach. You have 'n' number of server controls, do you need all 'n' numbers to be server controls and not just plain HTML?