Friday, February 3rd, 2006
A Comparison of Ajax Frameworks for ASP.NET
> As highlighted in this post on the Ajax.NET Professional blog today, there’s a comparison posted of several of the popular Ajax frameworks for those working with ASP.NET (created by Daniel Zeiss).
First, let me explain why only these 6 Frameworks are included although there is a lot more AJAX stuff for ASP.NET out there. All the frameworks listed here have one unique AJAX feature: They allow updating page content without programming AJAX directly – i call it indirect AJAX programming – a compareable concept is called Hijax.
Therefore, frameworks that supply only controls with built in AJAX-features (Trees, Grids, Lists and so on…) are not included in the comparison. Please forgive me and drop me a note if I forgot a framework that also allows indirect AJAX programming.
The list for the comparison includes:
- ComfortASP.NET V0.45 (beta)
- MagicAJAX.NET V0.2.2
- ComponentArt V3.0 Callback Control
- and more…
He has very detailed charts covering different topics like general information about the package, it’s ASP.NET compatibility, how much “traffic” it generates with its requests, and other additional features. There’s even charts for the traffic (in bytes) for a few different tests he performs with each package.
Related Content:











Interesting. Note, they left out Anthem ( http://anthem-dot-net.sourceforge.net/ ). Now if I could only decide which of these asp.net ajax framework meets my needs (ajax.net, anthem, atlas) and how to integrate the other great functionality found it other ajax frameworks, toolkits (dojo, scriptilicious, etc).
[...] Ajaxian » A Comparison of Ajax Frameworks for ASP.NET [...]
This is stupid.
Ajax is dead simple, who the hell needs a framework?
You could use a framework to avoid dealing with low-level XmlHttpRequests and therefore have more time to spend on your business logic.
What are the advantages of these frameworks against prototype with some extensions?
1. You can program everything in whatever server-side language and model you prefer.
2. You don’t need to write web services.
3. You don’t need to write DHTML.
4. The framework is very light-weight (~10K).
Yah they left out Anthem.Net (which is FREE) by Jason Diamond.
I found a new community set up for it at: http://www.anthemdotnet.com/
I’d say download the controls and try them out! Great simplicity and yet still very robust …
Add one more to the Ajax nuts and bolts mix:
Telerik has released the first third-party component suite offering support for the Microsoft “Atlas” Framework.
Ajax.Net is the framework that I am using as of now. Recenlty read about Anthem.net, will look into that too. Right now I ma using ajax to build a rating system similar to the one of this page.
zumiPage – The most easiest and powerful AJAX for ASP.NET
http://www.zumipage.com
They have left out a lot of interesting frameworks and libraries. For example since April I’m heavily using Ajaxium – a component which makes whole ASP.NET pages with all controls AJAX-ed (I mean really all control – my own, infragistics’ controls I’ve downloaded from codeproject). Also comparison misses a lot of important features – what about AJAX-ed navigation from one ASP.NET page to another? Is it impossible for most of frameworks and so omitted? What about smart downgrade to the old ASP.NET for old browsers and search spiders?
Take a look at this AJAX ASP.NET library, I think you’ll find it interesting as I did months ago.
Wulf Menger
These are not really frameworks, I would call them technologies. I have wrapped up a bunch of these open source technologies into a framework that gives an ASP.NET developer a starting point for building an AJAX app. See http://easyframe.sberringer.net. It’s open source.