Rex, I suspect a good place to start looking is solutions that compress the ViewState — they’re grabbing ViewState on the server before it’s sent down to the client and gzipping it. That’s exactly where you want to be. Scott Hanselman on ViewState Compression (2005) ViewState Compression with System.IO.Compression (2007)
To fire CheckedChanged event set the following properties for CheckBox, AutoPostBack property should be true and should have a default value either checked false or true. AutoPostBack=”true” Checked=”false”
First of all, the Mojarra implementation unintentionally swapped the meaning of those context parameters. So if you have the impression that the description is exactly the other way round than what the literal context parameter name implies, then this is indeed true. com.sun.faces.numberOfLogicalViews This is basically GET request based. Every GET request creates a new … Read more
If the search object isn’t huge in size, then go with using a ViewState. A ViewState is perfect if you only want the object to live for the current page’s lifecycle. A session object is also fine to use, but obviously once the search object is in there, it will be around for longer the … Read more
Microsoft says to never use a key generator web site. Like everyone else here, I added this to my web.config. <System.Web> <machineKey decryptionKey=”ABC123…SUPERLONGKEY…5432JFEI242″ validationKey=”XYZ234…SUPERLONGVALIDATIONKEY…FDA” validation=”SHA1″ /> </system.web> However, I used IIS as my machineKey generator like so: Open IIS and select a website to get this screen: Double click the Machine Key icon to get … Read more
But of course it can. In fact, the web is stateless. Any thoughts to the contrary are the aberration, in fact. Web Controls are gone in MVC. There are no events firing on the server side. This is replaced by two different mechanisms–URLs and POSTing form data. Proper use of these will replace your need … Read more
Well it depends. Invalid viewstate can happen for a variety of reasons. Viewstate is too big and has not finished rendering before a user causes a postback on the page. The fix is generally to disable all controls that trigger postbacks and enable them client side once the page has finished loading – see http://blogs.msdn.com/tom/archive/2008/03/14/validation-of-viewstate-mac-failed-error.aspx … Read more
This appears to be the same IE8 issue that many people have been experiencing. What appears to happen is that somehow IE8 (in both IE8 rendering mode and IE7 compatibility mode) will lose 4096 bytes out of the middle of the HTML document and this missing data causes this exception (you usually see this in … Read more
Here’s an online ViewState decoder: http://ignatu.co.uk/ViewStateDecoder.aspx Edit: Unfortunatey, the above link is dead – here’s another ViewState decoder (from the comments): http://viewstatedecoder.azurewebsites.net/