viewstate

I have a few questions about when and how viewstate is encrypted in asp.net 3.5. For instance, if I have a machinekey entry in my web.config like: decryptionKey="AutoGenerate,IsolateApps" validation="AES" decryption="Auto" /> Is viewstate encrypted at this point? Or do I need to specify the viewStateEncryptionMode in the page section also? Also, is it possible to encrypt a formsauthentication cookie, but not encrypt viewstate at the same time? Thanks for any help. The controls on the page can request that encryption be used for the ViewState, but even this request can be overridden by the page

I am learning ASP.NET MVC and many concepts of "ASP.NET" like authentication, authorization, session state still apply to it. But from whatever little I have understood, I don't see that ViewState is still relevant in an ASP.NET application. But it is there (property of System.Web.Mvc.ViewPage)! Is it there only for compatibility reasons or it still have some purpose/use? Dzmitry Huba Yes, that is correct. ViewState is not relevant. More on differencies between Page Model and MVC here: Compatibility of ASP.NET Web Forms and ASP.NET MVC Its present because ViewPage inherits from Page. However

In my ASP.NET application, I am loading an .ascx dynamically using LoadControl, using the following pattern: var ctrl = LoadControl("/path/to/control.ascx"); ((ControlType)ctrl).SomeProperty = someData; placeholder.Controls.Add(ctrl); The control that I add saves the SomeProperty property value directly to ViewState, as follows: public int? SomeProperty { get { return (int?)ViewState["SomeProperty"]; } set { ViewState["SomeProperty"] = value; } } After that, the ascx control lives a life on its own and all is well until postback occurs. When the page posts back, suddenly the view state is

I did follow the article TRULLY Understanding ViewState (great article btw) and populating my drop down list is working great. I've even setup a OnSelectedIndexChange event which fires almost as great. The problem I've found is the SelectedIndexChanged event won't fire when selecting the 0th index. It does all other times however. Here's some code: <asp:DropDownList runat="server" ID="DropDownList1" EnableViewState="false" AutoPostBack="True" OnSelectedIndexChanged="DropDownList1_SelectedIndexChanged" /> protected override void OnInit(EventArgs e) { this.DropDownList1.DataTextField = "Text";

alt text http://img3.imageshack.us/img3/1488/advancedsearch.png I'm building an "Advanced Search" interface in an ASP.NET application. I don't need SO to write this thing for me, but I'm stuck on a specific problem regarding dynamic controls and ViewState. I would like some direction for how to approach this. Here's my situation: Ingredients: A serviceable set of API objects representing entities, fields, and searches, which handles constructing a search, generating SQL, and returning the results. So that's all taken care of. ASP.NET 3.5 Desired Interface Functionality: (1) On initial page

I face this error from time to time, ExecuteStep at line:0 at Column:0 The state information is invalid for this page and might be corrupted. (*)Invalid viewstate Inner exception: unhandled exception in Application_Error At Load at line:0 at Column:0 Invalid length for a Base-64 char array or string debugging is enabled, and the pdb file exists, and as you see the debug info does not exactly tell me where it happened. I'm using ASP.NET, C#, DotNet 4.5 this only occurs on a specific page's load. [FormatException: Invalid length for a Base-64 char array or string.] System.Convert.FromBase64

I'm running into an issue with an ASP.NET 2.0 application. Our network folks just upped our security, and now I get the floowing error whenever I try to access the app: "This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms." I've done a little research, and it sounds like ASP.NET uses the RijndaelManaged AES encryption algorithm to encrypt the ViewState of pages... and RijndaelManaged is on the list of algorithms that aren't FIPS compliant. We're certainly not explicitly calling any encryption algorithm... much less anything on the non-compliant list.