ASP.NET Ajax Control Kit versus JQuery -
In the last 2 years, JQuery has become more and more popular. So, do you think, now ASP.NET projects with AGX have time to like JQuery like ASP.Net Ajax? ASP.NET AZ Control Kit Is A Future In ASPNET World?
short answer:
If your page / site is currently running UpdatePanel or ACT controls Definitely use jQuery and jQuery UI for any new task It is still Microsoft's own recommendation.
Long answer:
When it is important to be clear about the terminology related to this topic.
ASP.NET is part of AJAX client-side, but also server-side also. System.Web.Extensions came from Atlas and was eventually integrated into ASP.NET 3.5. Even if you do not use a ScriptManager or MicrosoftAjax.js, then the server-side part of ASP.NET AJAX is still creating JSON-based server-side end points (and which are not, there are no ScriptManager) Very useful for
jQuery and MicrosoftAjax.js are something similar, but both of these things that others do not do it right to say that they compete with each other; They have different goals if you have any update panels in your app, then you have Microsoft AJAX. There is no option to include JS (which is coming automatically with the script manager). JQuery and Microsoft AJAX JS play well together, so you can still do it.
AJX Control Toolkit (ATC) is a separate project, which is completely different from ASP.NET AJAX. It compares directly with the jQuery UI, not just in the core of jQuery. Going forward, I think we will only look at the client-side-only AJAX control toolkit controls that have been reintroduced in the form of jQuery plugins (which have already been late since last year, but they were dragged Was).
Finally, it is best to favor jQuery or jQuery UI on MicrosoftAjax.js or ACT if the equivalent solution exists in both. However, if you are bound to MicrosoftAjax.js with UpdatePanels or other existing code, then frighten the jQuery mix with that and the transition to jQuery gradually they work great.
Comments
Post a Comment