Web: ASP.NET AJAX

This post is number three in a three part series about memory consumption for web applications. Links to Part 1 and Part 2. Memory Consumption - Best Practices To be perfectly honest there is only one issue with memory consumption, i.e. using too much of it. Size does matter. Therefore every web developer should try and minimize the impact on the usage of memory, especially when the application tends to become huge. Web applications are becoming more and more client-side oriented and staying on one and the same page for hours should not be an exception. Therefore careful creation of new objects, managing the...

This post is number two in a three part series about memory consumption for web applications in general. Click here to read the first post. Memory leak examples In this post, we will look at different examples of leaks. The examples presented are as close as possible to real situations. Their purpose is to present several patterns that usually cause memory leaks. A way to manage the leakage is given along with the examples. The examples rely on the use of the ASP.NET AJAX Framework. Let’s start with a simple example of attaching a click event to a button element: Attaching event handlers HTML: <form id="form1" runat="server">        <asp:ScriptManager ID="theScriptManager" runat="server" />        <div id="buttonContainer">              ...

A customer of ours faced a very interesting issue we were able to solve earlier today.   The problem was that when Visual Studio run under the context of his account, all the Telerik VSExtensions were available in the Extension Manager. On the other hand, when Visual Studio run as a different user, the Telerik WebUI VSExtensions were missing.   The problem is very likely to happen if you run Visual Studio under different accounts to test your applications with limited permissions. It happens when you usually install the Telerik VSExtensions through the installer and you decide to install a newer version through the Extension Manager:   The...

This post is number one in a three part series about memory consumption for web applications in general. Since the Web 2.0 era, Web Applications have changed for the better. They provide more functionality, better usability and improved performance. However this tendency led to increased complexity. It is not unusual for a user to stay on a single page for hours without leaving. The browser would just poll data from the server through Ajax requests and display it in even more interesting manners. Therefore it is no wonder that web applications have become hungrier for resources and the browsers couldn’t...

The development for both desktop and mobile browsers has always been a difficult task, often an impossible one. To ease the process, we have prepared a couple of extenders, thus delivering to the developers unified methods to implement solutions for the mobile web platforms. In addition to the previously introduced TouchScrollExtender in Q3 2010, we present to you another member of the family. The ResizeExtender is a small client-side only control that enables resize and drag functionality on an HTML element in all browsers regardless if they are desktop or mobile (except the browsers that lack the needed desktop or touch events...