Is it possible to make the viewstate false of whole page including all controls at a time.I mean I don't want to set enableviewstate="false" for all controls..In the page directive of the aspx page I have made enableviewstate="false" but still viewstate of all the controls of the is enabled.. And what the EnableViewState="False"actually works within Page directive.
View 3 RepliesI have a page that has two drop down lists on it and a button. All controls sit in an update panel. The first drop down list (ddl1) contains a lot of values which caused a huge viewstate so I disabled viewstate on it. In the page oninit event I populate the drop down list every time the page is posted back. This all seems to work fine, it shows all the values and I can access the selected value in my event handler.
ddl1 has the autopostback attribute set to true so when its value changes the second drop down list (ddl2) is populated with some values that depend on the selection in ddl1. This also works fine, the values in ddl2 change when I select a value in ddl1.
ddl2 does not have viewstate disabled. The button that sits under my two drop down lists is disabled by default and becomes enabled when the value of ddl2 is changed to anything except string.empty. This is where I run into problems. ddl2 does an autopostback too but it seems to lose the selected index/value. When I'm in my code to check whether to enable or disable the button the selected index is always 0 and the selected value is string.Empty.
If I enable viewstate on ddl1 this all works fine. Could anyone point me to what I'm doing wrong?
Here is the code executed by the ddl2 postback:
[Code]....
I thought disabling ViewState for a server control would cause this control not to keep its state after a postback. I thought the same would happen if I disable ViewState for the whole page.
However, I tried to create an example to show this to a colleague and was puzzled when a textbox on a page would keep is state (in this case its Text property) after one or more postbacks, even when ViewState is disabled everywhere (both at Page level and Server Control level). Please see the code below:
[Code]....
I can keep pressing the Post back! button and every value typed on the textbox is still there after the postback(s). I'm using VS 2008.
After this example I now assume I don't understand ViewState as I thought I was.
I have a question regarding disabling viewstate.
I know how to do this in the page, however if I disable in a master page will all child pages and controls be disabled through inheritance?
The sites I mantain are using way too much ViewState and I'd like to reduce that so the size of the page is reduced. I've done a lot to remedy this but I have an issue relating to DropDown lists that use AutoPostbacks.I have a dropdown list with a lot of list items and a good part of the ViewState usage is to hold the list item data. If I disable ViewState and set the AutoPostBack property to true, the page will post back and in the page load I am trying to repopulate the dropdown list with cached data. However, it seems that the SelectedIndexChanged event doesn't fire when EnableViewState="false".Is it possible to make this work without enabling ViewState for the drodown list?
View 6 RepliesI have a web page which is using PasswordRecovery control.Its working fine but I have a scenario in which I have to disable Viewstate for the whole application.Now after disabling viewstate when I visit the webpage I have noticed that PasswordRecovery controls is not working (Every times when I submit the default button to go to step 2, the postback occur but not moving to step 2).
View 3 RepliesI have been getting this error a lot lately with some of my users, and I had a couple of concerns with view state and I have read so many articles but I am still lost..
1. I use masterpage on all the pages and I need viewstate for some of the pages but..
There is a page where a user will fill out the information and then submit this data to a cgi server, and it is where I get most of the Client Disconnected errors, what would happen if I disable viewstate when they click on that button?
Now when a user browses from one page to another, does the view state from the previous page get deleted? If not how would I delete it?
Does the master page have its own viewstate? Would I be able to make sure none of items on my master page are using the viewstate?
I have a shopping cart page (Cart.aspx) that has a button that will (sometimes) post to a third party payment gateway, if payment is necessary. The payment gateway will process the payment and then do a silent post to my website (Order.aspx) so I can update the order status.
Order.aspx always throws an invalid viewstate error, even though viewstate is disabled on the page.
What's happening is that Cart.aspx (which has viewstate enabled) posts to the payment gateway, and the gateway will post it back as part of the silent post. Even though Order.aspx has viewstate disabled and validation disabled, it still tries to validate the __viewstate field it's being given.
I know setting EnableViewState=false will disable the rendering of the __viewstate field, but if another page provides the field, shouldn't it still skip validation? I tried calling ViewState.Clear() on the Page_Init event of Order.aspx, but ViewState is apparently empty. how to get around this? I don't want to disable ViewState on Cart.aspx (in some cases it may be necessary), but I can't figure out how to clear it on Order.aspx.
I am using a custom error page in IIS 6:<customErrors redirectMode="ResponseRedirect" mode="On" defaultRedirect="Error2.aspx"/>I want to disable authentication for the custom error page because the error being raised is related to an authentication module and I don't want to get into an infinite loop and I want to display a clean error page to the user. I have been trying the following configuration to do that.
<location path="Error2.aspx">
<system.web>
<authentication mode="None"/>
[code]...
I have to disable our parent page(Complete gray out and non functioning) when child page is loaded. Once I close child page then I could perform any action at my parent page.
I can not use Div at my parent page because it may be many page so i have to controlled it from child page only.
Basically, the reason I am disabling the cache is because I have DevExpress ASPxGridViews, which work great for filtering, sorting, etc. but the client is working with large amounts of data and has requested that we save the filter/sort between page navigations.
The way this is done is via an event that occurs, ClientLayout. The problem is, when the user navigates to a different page, and then clicks the browsers Back button, the events do not fire, and the unfiltered grid is displayed, presumably because this is what was cached. (However a link back to the grid's page causes the page to load properly, and the events to fire.)
The only way I have been able to solve the problem is to disable caching as pointed out in this link:
http://forums.asp.net/p/1304752/2563283.aspx
Obviously, just because I CAN do it, doesn't mean its a good idea. I understand it might affect performance a bit, but can anyone tell me of any other problems that might occur? Maybe AJAX problems or controls giving out unexpected behaviour?
Can I disable all properties of an Internet Explorer when it opens a particular page called "help.aspx".I want that no option should be displayed on that page,just the content of the page which include the image of a person.
View 1 RepliesI am trying to disable and enable hyperlinks on an aspx page using a button from another aspx page. I have an idea of having two buttons on one page labelled "disable" and "enable". clicking disable should disable a particular link on another page and clicking enable should enable that same link.
View 5 RepliesIn my css I have defined:
Code:
#overlay
{
position: fixed;
height: 100%;
width: 100%;
z-index: 1000000;
[Code] ...
And then back on my client I have:
Code:
$("#Button1").click(function () {
var fileName = $("#MainContent_FileUpload1").attr("value");
var jsonData = '{ "fileName" : "' + encodeURI(fileName) + '"}';
if (checkFileExtension(fileName)) {
[Code] ...
Why my overlay doesn't display.
How to Disabling the form elements until the page is rendered completely.
View 1 RepliesWhat ASP.NET page lifecycle event can I write code in to determine the size of the viewstate that being sent out? Also, is it possible to determine the size without parsing through the rendered HTML (like a property on the page object) or is parsing the only way?
What I'd like to do is log the sizes, specifically if they cross a certain threshold.
Now here is the weird thing. First i am running it locally on the built in vs2008 web server.I load my control in fine, do a postback from a linkbutton, locally on my machine it all works fine, no issue.However when it goes onto my host, it falls over with the message:
Failed to load viewstate. The control tree into which viewstate is being loaded must match the control tree that was used to save viewstate during the previous request.Now i also load controls dynamically and use postbacks and things in the admin area of the site...and that works fine, however my front end just keeps failing? See the code behing below:
[Code]....
I have problem getting values from viewstate in GetTopThemes.
<asp:ObjectDataSource
ID="sourceGetTopThemes"
runat="server"
TypeName="DBConnection"
SelectMethod="GetTopThemes"
EnableViewState="true"></asp:ObjectDataSource>
[Code]....
}
[Code]....
when the page is not Posted back, I saved all values in the viewstate.
I have a clarification on Viewstate. I have used the Viewstate machanisum to save the data in particular page. I have to get my viewstate data from one page to another page. How can i get the values? First let me know Is it possible? I have gone over many articles. i did not clear with it.I have an aother option for it. Thats Session. I need not use this techinque. Please provide more information about the viewstate..
View 3 RepliesI stored a object in viewstate on Page. Now when i access the same viewsate object on usercontrol,it shows as null. I even tried creating the same viewstate with same name in usercontrol and page.Both holds different value. I understand that viewstate is a protected property. How does this thing implement in above scenerio or is there any other reason for this behaviour.
Edit:
Usercontrol is there in the page markup. I am not loading it dynamically. I have a page EditFacilityworkType.aspx. On page I have a usercontrol FacilityWorkTypeDetails.aspx(FacilityWorkTypeDetails1). Inside this usercontrol i have a user control Workflow.aspx(Workflow1)
Page_Load() of Page I am retrieving workflowdetails on page_load() of page.
FacilityWorktype facilityWorkType = facilityDetails.GetFacilityWorktypeDetail(SessionHelper.FacilityWorkTypeID);
ViewState["WorkFlow"] = facilityWorkType.FacilityWorkTypeWorkFlow
Inside usercontrol FacilityWorkTypeDetails.aspx. I have a property
public FacilityWorktype FacilityWorkTypeDetails
{
get
{
#region Fill FacilityWorktype
return GetEntityFromControl();
#endregion
}
set
{
PopulateControls(value);
}
}
Now i set this property in page load of page
FacilityWorkTypeDetails1.FacilityWorkTypeDetails = facilityWorkType;
Inside Workflow.aspx, I have a property
/// <summary>
/// Property to fill entity object from controls on this page
/// </summary>
public WorkFlow WorkFlowDetails
{
get
{
return GetEntityFromControls();
}
set
{
BindTranscriptionMethodDDL(ddlTranscMethod);
PopulateControls(value);
}
}
Now PopulateControls() of FacilityWorkTypeDetails1, i am setting property of workflow1
private void PopulateControls(FacilityWorktype value)
{
Workflow1.WorkFlowDetails = value.FacilityWorkTypeWorkFlow;
}
Now when i am retrieving values from
private WorkFlow GetEntityFromControls()
{
WorkFlow workFlow = (ViewState["WorkFlow"] as WorkFlow) ?? new WorkFlow();
//workFlow is null
}
So now inside this function workFlow is null. I want to ask,why is it null when i have set viewstate in page.
What are the latest and greatest ways to move ViewState to bottom of the page Can this be done in a IHttpHandler that can be specified in the web.config to intercept requests to "*.aspx"?
<httpHandlers>
<add verb="*" path="*.aspx" type="MyApp.OptimizedPageHandler" />
<httpHandlers>
Other options is that this could be done in a IHttpModule, but that is not as performant, as it will intercept all requests. Also it could be done in an a class deriving from the Page or MasterPage-class, but this is not as modular.Are there any performance penalties to this?
I have a page in ASP.NET.I have a nested class inside the page.I have a property in this nested class.How can I access the page's viewstate from the property's Set statement?
View 2 RepliesIf I disable ViewState at Page level, will it be remembered for GridView inside the page?
View 1 RepliesWhen you create an ASP.NET page with no controls and runs it, a view state hidden field is added.
Looking at what's in it (with ViewStateDecorder) reveals that there's a single value there that contains a number.
My question is - what is this number?
P.S. I guess this value appears on every page, with or without controls.
I've got a master page with a section for subnavigation links on it:
<div id="sub_nav" runat="server"></div>
I programatically populate this with Hyperlinks when my main asp:Menu data is bound depending on the address of the page I'm on.
This works fine and all my correct submenu stuff shows up on each page. The problem is that when one of these pages does a postback, I lose all the links that were in my sub_nav div.
Now, I could just populate the div with links every time regardless of whether the master page load is a postback or not, but I figured there is a better way of doing this. I was thinking enabling the viewstate on the div and links inside it might persist them through postbacks, but apparently that is not how viewstate works.