Menu
Under what circumstances would you use MicrosoftAjax over jQuery in an ASP.NET MVC application?
According to Scott Cate in this podcast Object Oriented AJAX with Scott Cate MicrosoftAjax is good for sending and retrieving data to and from the server. And jQuery is good for manipulating your data via the DOM once it arrives at the client. Yet, with a simple form plugin for jQuery you can send and retrieve data with jQuery quite easily. Often with a single line of code.
So I'm wondering what the difference is between MicrosoftAjax and jQuery within ASP.NET MVC?
873
The popular JavaScript framework, jQuery, is no exception. The popularity of jQuery as an easy-to-use JavaScript library used from any web development platform makes the ability to be used with the upcoming ASP.NET MVC Framework especially attractive.
ASP.NET MVC is a technology used to create websites that run on Microsoft Internet Information Services (IIS). JavaScript is a computer language used to add interactive operations to a webpage. jQuery is a library based on JavaScript to enhance the language to create highly functional websites and webpages.
MVC 6 is a part of ASP.NET 5 that has been designed for cloud-optimized applications. The runtime automatically picks the correct version of the library when our MVC application is deployed to the cloud. The Core CLR is also supposed to be tuned with a high resource-efficient optimization.
Go with jQuery - even Microsoft has seen the error of their ways. The next version of Visual Studio will include jQuery and support it with intellisense. You're also entirely correct regarding the simple plugin. MS Ajax, while sometimes easier to work with initially, is slow and bloated.
90
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
