Microsoft AJAX Client Library vs jQuery

Question

A lot of discussion happens with jQuery and MS Ajax after the built-in jquery news.

I am currently convincing my team to consider jQuery, but I am not professional in any of these.

I really need good comparisons between the jQuery library and MS Ajax Client, as my team claims that we can use jQuery if we just use the raw ms ajax client library, and jQuery seems to have a better selector.

Can someone give some idea on why using jQuery than MS Ajax in some scenarios? if the problem is work efficiency?

Thanks!

Answer 1

I use both. I think these two are intended for different use cases - MS AJAX is designed to transfer some data from server to client at boot time (ScriptControl) and to create source associations of controls. In addition, web service wrappers are extremely useful for AJAX data, and wrappers depend on the MS AJAX library.

And jQuery for crawling / modifying the DOM after loading the page. MS AJAX can do this, but much more complicated than jQuery. In addition, jQuery as a framework provides access to a ton of plugins - client scripts and controls such as menus / trees, etc.

Answer 2

SO Question: Pros and cons of MS Ajax vs jQuery in an ASP.NET MVC application?

Answer 3

Microsoft is now submitting jQuery as part of Asp.net MVC. They will not use jQuery internally, but promote it. Check out this article.

Answer 4

We need to ask - why are we using ASP.NET? Mostly because of the controls it provides. If jQuery provides controls as plugins, then there is no need for ASP.NET or Microsoft AJAX tools. If we create our site based on pure HTML pages, use jQuery to control the dynamic part of the HTML page and, finally, using WebService to store / retrieve information from the database, then we completely eliminate ASP.NET ASP.NET slows down the site. since your request goes through many steps to access the compiled ASPX page, which is then parsed, then the code and designer files are combined and then finally HTML is displayed.

Some might argue that Microsoft provides MasterPages. Think about using MasterPages as they slow down your site too much. Each page request restores the entire MasterPage. Instead, try using IFRAMES. Submit your start page with all the navigation controls with the content area in IFRAME format. This content area should load the proper HTML page based on a click on the user menu.