viewstate

I have a site that features some pages which do not require any post-back functionality. They simply display static HTML and don't even have any associated code. However, since the Master Page has a <form runat="server"> tag which wraps all ContentPlaceHolder s, the resulting HTML always contains the ViewState field, i.e: <input type="hidden" id="__VIEWSTATE" value="/wEPDwUKMjEwNDQyMTMxM2Rk0XhpfvawD3g+fsmZqmeRoPnb9kI=" /> EDIT: I tried both variants of setting EnableViewState on page level with no luck at all: <%@ Page Language="C#" EnableViewState="false" %> <%@ Page Language="C#"

I have a list of type List<JobSeeker> . I want to store it in ViewState. How this can be done? private List<JobSeeker> JobSeekersList { get; set; } Basically you only need to use the get , then on get you either get the posted data from view state, or set it for the first time on the view state. This is the more robust code to avoid all the checks on each call (is view state set, exist etc), and direct saved and use the view state object. // using this const you avoid bugs in mispelling the correct key. const string cJobSeekerNameConst = "JobSeeker_cnst"; public List<JobSeeker> JobSeekersList

I have the following in my BasePage class which all my ASPX pages derive from: protected override void OnInit(EventArgs e) { base.OnInit(e); ViewStateUserKey = Session.SessionID; } I also have a machineKey set in Web.config . I don't think this error is because of a web farm because this happens on my dev machine too. My host has now upgraded to .NET 3.5 SP1. After this update, everytime I compile with the ViewStateUserKey setting above, I constantly get the "Validation of viewstate MAC failed" error on every postback. What am I doing wrong here? Is this setting even necessary anymore with the

Let's say you have a aspx page that does not rely on session, but does rely on viewstate for persistance between postbacks. If a user is accessing this page, and leaves for a long lunch, will viewstate still be valid when he returns? No ViewState is kept as part of the PostBack process. You can, however, override the Page class's SavePageStateToPersistenceMedium() and LoadPageStateFromPersistenceMedium(), to implement that behavior if desired. For more information read Understanding the ASP.NET ViewState . Note that Page ViewState is stored in the Session so if your Session expires, the

I have an ASP.NET 2.0 application that is working fine in our local environment. When published to a test server, we're getting intermittent errors on the server. Here's the most common: Padding is invalid and cannot be removed. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Security.Cryptography.CryptographicException: Padding is invalid and cannot be removed. Source Error: An unhandled exception was generated during