There are a lot of great reasons for businesses to deploy their solutions as Web applications. While these reasons have changed over the years, some of the most critical ones remain. The chief is almost always the ease of deployment. Because there is no installer to be run on every client, there are also no headaches with drivers provided a compatible browser is available on the client.
Browser availability is definitely something we can take for granted these days, removing an early objection to Web applications over native programs. Versioning is also a dream with a Web application compared to a native one: just update the files on the Web server, and your new features are available to the world.
There are, of course, disadvantages with Web applications as well. Chief among these is that the user interface depends on network latency often held hostage to the quality of the connection between the browser and the Web server. This architecture meant that early websites would collect as much information as possible before causing the postback to the Web server, denoted by the screen blink that can be so disconcerting to the user.
Screen refreshing aside, there are other big issues with this approach. If something goes wrong, the loss to the user is maximized instead of minimized. We have all filled out Web forms with lots of information, only to have something go wrong and force us to enter it all again when the page resets after the error. This caused developers and their managers to choose sides in the native application vs. Web application argument that still rages today. There are still drawbacks to browser-based applications, but these issues are mitigated by the techniques and technologies we now call AJAX.
Soon after its introduction, AJAX became one of the major buzzwords of Web development. By shifting interactive functionality to the client and allowing behind-the-scenes communications with the Web server for partial page updates, Web-based systems became much less dependent on wholesale, round-trip page refreshes for their responsiveness. Component providers rushed to fill the space; in fact, Telerik vice president Chris Sells noted that his company’s first commercial offering was a set of AJAX-based controls named RadControls for ASP.NET AJAX. Since then, the ecosystem for .NET developer tools has become packed with offerings in this area, though many are using a variety of techniques and libraries.
AJAX Control Toolkit
Microsoft’s support for AJAX controls was an effort to catch up tp a thing that caught on by surprise. Eventually, like so many libraries and frameworks, it gave it a life of its own by making it an open-source project. This past January, Microsoft released an update to the AJAX Control Kit, including new chart controls. Available via NuGet and hosted on Codeplex, there are more than 40 controls with both basic and advanced functionality. These controls satisfy basic needs and act as a great starter kit.