viewstate

问题 We have a system which dynamically creates the controls of a page every post back and handles back using the browser history and such. The problem is that on the production server (2 nodes on NLB) we get randomly in differnet spots with no correlation we have found, a failed to load viewstate, the control tree might be different error. However, the exact same code on our staging server (same NLB setup as production) this has never happened. I'm basically ruling out that its code at this point

问题 We have a system which dynamically creates the controls of a page every post back and handles back using the browser history and such. The problem is that on the production server (2 nodes on NLB) we get randomly in differnet spots with no correlation we have found, a failed to load viewstate, the control tree might be different error. However, the exact same code on our staging server (same NLB setup as production) this has never happened. I'm basically ruling out that its code at this point

问题 I'm having trouble decoding a ASP.NET view state string in Python 3. When I try decoding the string using bash's base64 command, it decodes the string successfully and I'm able to see all the information I need (most of it is in Hebrew, meaning UTF-8). The view state is of course base64-encoded only and not encrypted. However, when I try do decode the string using Python's base64 library and then decoding the byte array to a UTF-8 string, I get an error message: UnicodeDecodeError: 'utf-8'

问题 I have a repeater in my page with some pre-conditions such as a checkbox list and listboxes that dictate what the datasource for the repeater brings back. A button is clicked which will databind the repeater which works fine. However if the user decides they want to add something else in or remove something they can check/uncheck some fields and then hit the button again which will rebind the repeater and change what is displayed, however the viewstate of all the current controls in the

问题 Here is a class that I wrote to solve some issues that I was having with viewstate. It stores the info in the users session and increments a value to track which state to show. The difficulty is that there is no support for the back button. The reason I originally had this was that before AJAX came along the viewstate was being send down to the client instead of being stored on the server. I figured that by storing it on the server i could make the client experience much richer. Now with

问题 i search many site but not getting any solution that how programatically detect ViewState. i got one suggestion from a site that they said EnableViewStateMac to true in the @Page directive and other settings like VaidationKey and ValidationAlgorithm has also to be defined. but they did not said how to do the settings like VaidationKey and ValidationAlgorithm. can anyone drive me in right direction. thanks 回答1: The EnableViewStateMac property is true by default in ASP.NET. When it is true it

问题 I'm getting a DataTable from a DataBase and assigning to ViewState like below: Because I don't want to hit the database for every time. DataTable dt = GetDataTable(); ViewState["dtTable"] = dt; GetDataTable() is a method, which retrieves 1000 records from the DataBase. Is this the best way or which one is the best way to handle this? 回答1: First things first: Explanations aside, It still depends a lot on your requirements, environments settings ... The viewstate is stored in a hidden field

问题 I'm getting a DataTable from a DataBase and assigning to ViewState like below: Because I don't want to hit the database for every time. DataTable dt = GetDataTable(); ViewState["dtTable"] = dt; GetDataTable() is a method, which retrieves 1000 records from the DataBase. Is this the best way or which one is the best way to handle this? 回答1: First things first: Explanations aside, It still depends a lot on your requirements, environments settings ... The viewstate is stored in a hidden field

问题 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? 回答1: Yes, that is correct. ViewState is not relevant. More on differencies between Page Model and MVC here: Compatibility

问题 I'm trying to clean up an older ASP.NET WebForms site that has ViewState enabled everywhere. This is a performance issue - huge viewstates cause noticeable submit delays. But most of the forms don't really seem to need ViewState except for some complex control & form data. Even forms with no input controls, though, generate big viewstates because I guess asp.net is storing all kinds of metatdata about every single server control. But the visibility state, etc, is all controlled in code so I