Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 08, 2009 06:55 AM by guenavan
Jan 02, 2009 10:21 PM|LINK
What is the difference? It seems like jquery is only for dom manipulation, not for building a client-side framework (components, classes, etc). So asp.net ajax seems to be the better approach if going for that, however I see that jquery is all the rave.
I recently read Daniel Larson's "Developing Service-Oriented AJAX Applications on the Microsoft Platform", which I thought was an excellent book and would like to use as a basis for writing my own client-framework. He doesn't use jquery at all. Would I benefit
from it? How would it fit into a design like is demonstrated in that book, as I really want to use his, but feel like I'd be missing out on jquery (but it seems more straightforward than jquery and why mix up the two in code anyway (since jquery looks pretty
different to me) - why not just use asp.net ajax)?? Anyone have any opinions?
Jan 02, 2009 11:47 PM|LINK
jQuery is basically like the ASP.NET AJAX Client Framework (MicrosoftAjax.js), with selectors, DOM manipulation, plugins, and better animation support. On the client side jQuery is really much more powerful than MS AJAX. That's why they've decided to start
bundling it with VS in the future, instead of trying to reinvent that wheel in MicrosoftAjax.js.
jQuery and ASP.NET AJAX aren't necessarily mutually exclusive though. For example, using MS AJAX to automatically JSON serialize the return from an ASMX service is very useful.
Take a look at the jQuery category on my blog for some examples of using jQuery on the client with ASP.NET AJAX on the server.
Jan 05, 2009 07:52 AM|LINK
ASP.Net Ajax and JQuery are different framework on client. You can use ASP.Net Ajax with JQuery if you'd like to. Please check this article by Scott Gu:
Feb 06, 2009 10:14 AM|LINK
I'm a newbie here, Can anyone tell me the pros and cons of using AJAX vs. jQuery with AJAX in asp.net applications?
Feb 09, 2009 01:21 AM|LINK
Feb 09, 2009 05:43 AM|LINK
May 04, 2009 10:44 AM|LINK
the XMLHttpRequest wrapper engine) in favor to jquery?
This appears to be confusing, because we now have 2 frameworks, 2 ways to do things.
May 04, 2009 12:48 PM|LINK
various other methods . And all of them primarly target dom manipulation . Whereas asp.net ajax offers more when it comes to overall application development . With ajax you can create server controls, extender's etc based on your requiremnets . I also prefer
asp.net ajax over jQuery whenever I have to make a db query using webmethods since it is more clean and easy to use . Already asp.net ajax 2.0 framework is out and 4.0 is on its way . Also I feel two is better than one . If you can understand where to use
jQuery and where to put ajax , then its a win win situation for you.
Dec 08, 2009 06:55 AM|LINK
With ajax you can create server controls, extender's etc based on your requiremnets . I also prefer asp.net ajax over jQuery whenever I have to make a db query using webmethods since it is more clean and easy to use
Already asp.net ajax 2.0 framework is out
(BUG: fanthom Version 126.96.36.199 of ASP.NET Ajax Extensions)