Microsoft Ajax Control Toolkit vs. jQuery

Question

Hi,

we are currently developing a couple of custom asp.net server controls. Now we'd like to add some Ajax support to some of them. Now basically there would be two options

• Microsoft Ajax & Microsoft Ajax Control Toolkit
• jQuery

I worked already with the Control Toolkit, writing a complete Extender and it was quite intuitive, once you understand the story behind. But I also like the simplicity of jQuery.

So I'd like to hear some of you what you would like to go for (advantages/disadvantages of each of them), considering also that we're mainly dealing with Microsoft technologies. Would you go more for the toolkit or jQuery,...or both?

//Edit:
I just made some tests and I have to admit that at the moment I find the Toolkit better due to the integration. My purpose is mainly for using it on the server controls, so with the toolkit I have corresponding classes on the server-side where I can do something like

CalendarExtender toolkitCalendarExtender = new CalendarExtender();
toolkitCalendarExtender.TargetControlID....
...

this.Controls.Add(toolkitCalendarExtender);

This is really nice because in this way I don't have to deal with rendering predefined JavaScript which I construct somehow as string inside my custom server control. With jQuery I would have to do so (except for the toolkit Nicolas mentioned, but the support there is too weak for using it in a professional environment)

Thanks a lot.

Answer 1

The first and most important point in my opinion is the user base for these two.

I think jQuery has a wide user group compared to Microsoft Ajax. So support for jQuery will be much more.

Answer 2

1. You have much more documentation for jQuery than for Microsoft ajax.
2. The jQuery user base is way bigger
3. You have plenty of plugins for jQuery
4. bonus: jQuery has a cool name :-)

Answer 3

While these might not be major points, I'll try. jQuery does not have an UpdatePanel - This is a good thing. Your jQuery skills would easily transfer to another stack like ASP.NET MVC, Django, or Rails. It's been a while since I've seen MS's Ajax docs, but jQuery's documentation is a huge factor for me - it's excellent.

I've heard of some developers using both libraries, that might be something to look into as well.

Answer 4

I occasionally use both. Sometimes the MS AJAX Toolkit is super handy for certain things and other times it's just a mess. jQuery is great for lots of things but can occasionally be limited.

I would, however, err on the side of jQuery since no matter what platform you go to, jQuery will always be applicable since it is completely client-based, whereas the MS AJAX Toolkit skills will not help you should you decide to try another server-side platform.

Answer 5

For me, I would use AjaxControlToolkit only when the jQuery plug-in does not exist. Moreover, with the use of jQuery control Toolkit, you can use jQuery with server controls. Have a look at it on codeplex

Answer 6

If you mainly code in MS Shops with Visual Studio, then the toolkit is the way to go, you will still need to know some javascript to do some things, but in this situation the toolkit allow really fast dev and some code behind support for certain controls. That said it never hurts to learn both, the toolkit is really strait forward so the learning curve is small and to some degree which mainly depends on your knowledge of javascript, so is jquery. Most apps I am seeing now a days uses both and it works quite well and once you learn enough of each you will be able to decide what to use where... basically both builds a bigger toolbox and big toolbox is always a great thing to have.

Answer 7

I was never thrilled with the ajax toolkit. It seemed clunky and bloated.

When I stumbled upon jQuery I never looked back...

Answer 8

Aren't web controls supposed to abstract client implementation to a certain degree? And if so, isn't it feasible the MS will implement the Ajax toolkit using jquery someday?

Jquery is slick and I like playing around with it, but there's also something very durable about web controls in that their implementation can get updated automatically alongside client technologies.