If I disable ViewState at Page level, will it be remembered for GridView inside the page?
If you disabled ViewState at the Page level all controls on that page will have ViewState disabled (i.e. won't be able to use any of the functionality provided by ViewState). I'm not sure from your question if you want GridView to have ViewState enabled and all other controls be disabled, but if that's what you want to do then you have two options:
If you are using .NET 4.0 then you can disabled ViewState on the page level and enable it just for the GridView
If you're using .NET version prior to .NET 4.0 then you have to explicitly disable ViewState for all controls (by adding EnableViewState='false' to all elements) and don't add that for GridView. You cannot disable it on Page level and enable for GridView only.
Related
How do I use the signal R when the information in the database has changed the entire page to reload?
Or how can one bind the grid view again?
I have an asp.net application where I have a radGrid control that displays records from a database. I would like the grid control to do client side caching (paging and sorting). However, I can only find one sample (Grid - Client-Side Binding and Caching) on Telerik's website, but it uses a webservice as a Databinding location source.
Has anyone had any experience with radGrid, clientside caching displaying data from a database?
I'm trying to debug some code and have a feeling that my UpdatePanel is disrupting my Silverlight xap control. There are times where my silverlight chart is not rendering and asking the user to download the silverlight plugin.
Has anyone experienced a problem with a .xap file being a child element of an UpdatePanel?
I have never had to put a Silverlight control within an UpdatePanel. Silverlight controls by nature should not be constantly reloaded like an UpdatePanel will want to do. Everytime an UpdatePanel triggers a refresh your Silverlight control will need to reload.
I would recommend removing the Silverlight control from the UpdatePanel if possible because there is nothing that the UpdatePanel adds to the functionality of the Silverlight control. If you need to trigger stuff from your UpdatePanel then just setup javascript hooks to your Silverlight control.
I set a reference to AjaxControlToolkit.dll and this added all of the toolkit's controls to my toolbar. I then tried to drag and drop one of the controls to my webform and nothing happened-no error message, no control added to the form. Double clicking the control also did nothing.
The web site compiles with no errors, I also tried to bounce VS2008. I am running Developers Edition on Windows Server 2008.
I was able to add a Script Manager control
This worked w/o issue on my other computers.
Also, make sure you drop the tools into the source tab of your ASP page. As many of these controls has no graphical representation.
Ajaxtoolkit controls in VS2008 are extenders of other controls. Add the parent control first.
In my last job we ended up rewriting the complete ASP.NET stack (forms, controls, validation, postback handling, ajax library etc...) - the reason I was given was that the ASP.NET controls were not accessible enough, not were any of the third party controls that were assessed for the project.
Can anyone point me to good accessible ASP.NET controls that do ajax as well?
Failing that, how would you approach creating accessible, ajax enabled controls?
You could take a look at the 'App_Browsers' feature in .NET.
It gives you the opportunity to hook into the rendering engine for each control. The original intention for this was to be able to alter the HTML output of controls depending on the user's browser - but you can also do it for all browsers.
You could also take a look at these control adapters, which make the normal ASP.NET controls 'CSS Friendly'.