For pages with a large ViewState, I\'d like to find out by which controls the ViewState was produced (which control produced how much ViewState).
I am looking for suggestions on the best way to save data for a multi-page user form between sessions. I am using c# 3.5 and SQL server 2008
I have a problem with the Event object being null when I want to fire the event. There are other threads here and on the net about this:
I\'ve an asp.net page which there is a multiview control inside. Within the control 开发者_高级运维there are many many textboxes, selects and dynamically created tables. Therefore, I believe I have to
I having a viewstate to store a data query from SharePoint, where the data might be very huge, the reason why I wanted to store in viewstate is for later filter on the queried data.
HI, I\'m working on DotNetNuke 5 module that basically consists of three pages; step 1, step2 and step3.
Our application uses ViewState for storing page level variables. We are planning to migrat开发者_如何学JAVAe the same to use PageContext. Are there any drawbacks of Page Context over ViewState or vice
This is 10KB in my HTML source: <input type=\"hidden\" name=\"__VIEWSTATE\" id=\"__VIEWSTATE\" value=\"/wEPDwUKLTEyOTAwODE4Nw9kFgJmD2QWAgIDD2QWBGYPZBYEAgEPDxYCHgdWaXNpYmxlaGRkAgIPZBYIAgEPFgIfAGdkA
if i set EnableViewState=\"false\" then also input data is maintain after postback at the time of using control like
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