blocks|key|3343864|text|就我个人而言，我会坚持使用JQuery。就大小而言，MS+AJAX是相当重量级的，您可以使用JQuery做很多事情。至于转换代码是否容易，这取决于你使用了多少MS+AJAX东西。我不认为两者在调试方面有太大的区别。您将拥有一个更大的JQuery用户社区，可以从中提取资源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3343865|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Personally, I would stick with JQuery. MS AJAX is pretty heavyweight in terms of size and you can do so much with JQuery. As far as whether it is easy to convert code, well it depends on how much of the MS AJAX stuff you are using. I don't think there is really much appreciable difference in debugging from one to the other. You will have a larger community of JQuery users from which to pull resources.

blocks|key|3343877|text|您可以根据需要同时使用这两个工具(我也是这样做的)。当我想要一个特定的表单是非javascript友好的，并且我在服务器上生成内容时，我会通过AjaxHelper使用MS+AJAX。它在客户端构建了我需要的一切，以处理不支持javascript的浏览器。我只需要检测控制器中的AJAX/非AJAX，并根据需要返回部分或全部视图。如果我需要使用AJAX作为插件的一部分(比如autocomplete)，那么我将使用jQuery。关键是我使用最适合(最容易实现)的工具。诚然，我的大多数应用程序都在内部网上运行，所以我不太关心下载量的大小。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3343878|entityMap^0|56|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You can (and I do) use both depending on the need. When I want a particular form to be non-javascript friendly AND I'm generating content on the server, I'll use MS AJAX via the AjaxHelper. It builds everything I need on the client side to handle the non-javascript enabled browser. I only need to detect AJAX/non-AJAX in the controller and return a partial or a full view depending. If I need to use AJAX as part of a plugin (say <code>autocomplete</code>), then I'll use jQuery. The point is I use the tool that best suited (easiest to implement) for me. Granted, most of my apps run on an intranet so I'm much less concerned about the size of the downloads.

blocks|key|3343905|text|我还找到了关于MS并入库的jQuery+announcement|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3343906|显然：|3343907|3343908|此外，微软将开发在jQuery上运行的额外控件或小部件，这些控件或小部件可以轻松地部署到.NET应用程序中。jQuery助手还将包含在.NET开发的服务器端部分(除了现有的助手之外)，为现有的ASP.NET+AJAX功能提供补充功能。|blockquote|3343909|3343910|3343911|因此，我认为他们很有可能最终拥有与MS的jQuery助手完全相同的AJAX助手。|3343912|我想我将采取的解决方案是使用Html.BeginForm，然后截取submit按钮来使用jQuery。我并不特别担心没有javascript的人会失去功能，但这也不是很难做到的。|3343913|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.jquery.com/2008/09/28/jquery-microsoft-nokia/^0|D|J|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|13|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|15|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|17|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]]]

I also found the <a href="http://blog.jquery.com/2008/09/28/jquery-microsoft-nokia/" rel="nofollow noreferrer">jQuery announcement</a> about MS incorporating the library

Apparently :

<blockquote>
 Additionally Microsoft will be
 developing additional controls, or
 widgets, to run on top of jQuery that
 will be easily deployable within your
 .NET applications. jQuery helpers will
 also be included in the server-side
 portion of .NET development (in
 addition to the existing helpers)
 providing complementary functions to
 existing ASP.NET AJAX capabilities.
</blockquote>

So I'm thinking its quite probable that they'll end up having jQuery helpers that exactly mirror the AJAX helpers for the MS stuff. 

I guess solution I'll take is to use Html.BeginForm, and then intercept the submit button to use jQuery. I'm not especially worried about people without javascript losing functionality, but its not that much harder to do so I may as well.

blocks|key|349268|text|JQuery比Ajax更容易编码，开销的问题可以通过添加更多的内存而不是流内嵌代码来解决。Ajax对我来说没有任何意义，尽管我还是个初学者。在处理了过于残缺的Ajax语法之后，jQuery就像一股新鲜空气。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|349269|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

JQuery is much easier to code than Ajax allot of the problems with overhead can be remedied by adding more memory rather than by stream lining code. Ajax just does not make any sense to me although I'm just a beginner at it. After dealing with the overly criptic Ajax syntax, jQuery is like a breath of freash air.

blocks|key|349271|text|嗯，我发现MS+Ajax框架中有一件事是不能用jQuery优雅地完成的。构建MS+Ajax的用户控件非常面向对象。使用jQuery很难做到这一点。例如，假设您正在构建一个"address“用户控件，它将包含address1、address2、city、state、zipcode和country。您可以使用jQuery和Ajax构建此控件，但Ajax库提供的好处是它将地址控件划分开来。您可以在该控件上定义一个函数"+reset+()“，用于重置address控件的内容。假设您希望"reset()“将address1、address2、City设置为空字符串，但将State设置为"AL”，将Country设置为USA。在(.js)文件中定义Ajax控件的代码，该函数将与您的address控件相关联。对于jQuery来说，这是不可能的。您定义的任何函数在作用域上都是全局的，并且没有简单的方法来绑定该函数的地址控制。您可以很好地在窗体的textbox控件上调用"reset“函数！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|349272|所以如果你想创建一个纯面向对象的用户控件，那么我想更好的选择是使用MS+Ajax框架。|349273|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well there is one thing that I found with MS Ajax framework that cannot be done elegantly with jQuery. User controls build MS Ajax are very object oriented. This cannot be easily done with jQuery. For example, lets assume you are building a "address" user control, that will have address1, address2, city, state, zipcode and country. You can build this control with jQuery and Ajax but the benefit that's provided by Ajax library is that it will compartmentalize the address control. You can define a function "reset()" on that control that would reset the contents of address control. Lets say that you want "reset()" to set address1, address2, City to Empty string but State to "AL" and Country to USA. You define the code for Ajax control in (.js) file and that function will be associated with your address control. Same is not possible with jQuery. Any function you define will be global in scope and there is no easy way to tie that function Address control. You can very well call the "reset" function on textbox control on the form!!!

So if you want to create a pure object oriented user controls then i guess better choice is using MS Ajax framework.

Now that RC1 is out I need to decide once and for all whether to use MS Ajax libraries or just jQuery for AJAX requests. The application is a new application. Essentially the way I'll decide is whether or not i get any significant benefit from the Microsoft libraries that I wouldn't get from jQuery. I already HAVE jQuery loading and I am concerned about the extra overhead of file size more than anything.

As far as I'm aware -- the only benefit really is that there are helpers like <code>Ajax.BeginForm</code>, but perhaps these will work with jQuery at some point anyway? I was also told today by a government employee friend of mine that MS Ajax library has a LOT of bugs in it - which concerns me.

With Microsoft now having officially <a href="http://weblogs.asp.net/scottgu/archive/2008/09/28/jquery-and-microsoft.aspx" rel="noreferrer">befriended jQuery</a> I wouldn't be too worried about them doing anything in future to leave jQuery in the dust by enhancing their own libraries.

I really don't know a whole lot about exactly what MS Ajax actually does for me. Are there certain pros and cons. Or is it just 90% bloat to support 'update panel' ?

I also find it very interesting that the <a href="http://www.manning.com/palermo/" rel="noreferrer">ASP.NET MVC in Action</a> book just skips over the MS Ajax libraries and jumps straight into jQuery :

<blockquote>
 In this chapter the reader will
 examine how the ajax technique is
 applied to ASP.NET MVC in a more
 seamless way than with Web Forms. The
 reader will see how to leverage an
 increasingly popular, lightweight
 javascript library called jQuery.
 
 (from <a href="http://www.manning.com/palermo/palermo_meapch9_sample.pdf" rel="noreferrer">free sample</a> chapter on AJAX)
</blockquote>

Would very much appreciate hearing from anyone about their experiences workin with both, expecially on the following additional questions :

<ul>
<li>is it easy to convert code between the two libraries - assuming relatively simple ajax requirements ? </li>
<li>is debugging notably better or faster in either library</li>
<li>anybody know how ASP.NET 4.0 is progressing and any announced plans for the AJAX library that might be beneficial to MVC?</li>
<li>what in a nutshell could MS AJAX do for an MVC app beyond sending requests and sticking the response in a DIV? </li>
<li>how do i do the equivalent of <code>Ajax.BeginForm(...)</code> and use jQuery ?</li>
<li>what was your deal killer one way or the other?</li>
<li>what are most people out there using?</li>
</ul>

Pros and cons of MS Ajax vs. jQuery in an ASP.NET MVC app?

服务器

jQuery

现在RC1已经出来了，我需要一劳永逸地决定是使用MS Ajax库，还是只对AJAX请求使用jQuery。该应用程序是一个新应用程序。本质上，我决定的方式是我是否从微软的库中获得了任何我不会从jQuery中获得的显着的好处。我已经加载了jQuery，我最关心的是文件大小的额外开销。据我所知--唯一的好处是有像Ajax.B...

问在ASP.NET MVC应用程序中MS Ajax与jQuery的优缺点？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ASP.NET MVC应用程序中MS Ajax与jQuery的优缺点？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ASP.NET MVC应用程序中MS Ajax与jQuery的优缺点？
EN