Support & Learning
Application Development and Deployment
Data Connectivity and Integration
Web Content Management
Get A Free Trial
close mobile menu
Testing & ALM
Tag: ASP.NET AJAX
Don't store ASP.NET controls in Session, Application or Cache
In some cases you may end up with the following exception when working with RadControls for ASP.NET Ajax: "Script controls may not be registered after PreRender." The explanation of this error is simple - some UI control implementing the IScriptControl interface (e.g. any control from the RadControls for ASP.NET Ajax suite) is stored in the Session, Application or Cache and then is added in some live controls collection. Here is an...
September 19, 2008
50% more ASP.NET skins
A big thank you guys! Tribute to the generosity of you, our community, we now have 50% more skins available for the telerik ASP.NET components. Check out the latest additions in our Skins Exchange Program and feel free to download a copy for your project. Also, don’t forget to vote for your favorite community skin – we have an Xbox and free RadControls licenses waiting for the winners. Voting will close on September, 15th. Once again, I would like to express our enormous gratitude to everyone who took the time to contribute their custom-made skins to the program. What started as a...
September 05, 2008
RadRotator for ASP.NET AJAX: Using dynamic templates
My colleague Todd Anglin has already written a post about how to create a rotator control dynamically - you can read it here - How to Create RadRotator Programmatically. Unfortunately, this code in that post is for the old RadRotator control and if you try to use it in the new ASP.NET AJAX version, you will notice that it will not compile. Fortunately, you can quickly fix that. Here is what you need to change: FrameTemplate - this property has been replaced with ItemTemplate RadRotatorFrame - this object has been replaced with RadRotatorItem After you update the above names, you should be able...
August 20, 2008
RadTreeView for ASP.NET Ajax Load On Demand Modes - why so many?
In my previous blog post I told you how the Web Service load on demand mode of RadTreeView delivers the best performance. A logical question arises - why we have the other load on demand modes (server side postback and callback) if they do not perform on par with the Web Service mode. The answer is not that obvious. The truth is every load on demand mode has its pros and cons. The following table describes visually the load on demand modes according to three criterions - performance, templates support, ease of...
August 08, 2008
Performance Tip: Use Web Service Load On Demand with RadTreeView
A common scenario for a treeview control is to populate it with lots of nodes. Adding a few thousand nodes initially is not a good idea though. Think of all the rendered HTML. Even rendering a few thousand strings (without any extra markup) will result in a few megabytes of HTML. That's where load on demand comes into play. RadTreeView supports three different types of load on demand: web service, server side callback and server side postback. From those the server-side postback mode is least efficient in terms of performance because it postbacks and updates the whole page. Here is how...
August 06, 2008
Testing & ALM
Latest updates in your inbox
How to Use ASP.NET Core TagHelpers
September 20, 2017
Build Once Deploy Everywhere with Telerik Reporting
September 19, 2017
Progress @ DEVintersection: Sessions, Product Showcases and Lots of Fun
October 02, 2017