jQuery and Microsoft

jQuery is a lightweight open source JavaScript library (only 15kb in size) that in a relatively short span of time has become one of the most popular libraries on the web.

A big part of the appeal of jQuery is that it allows you to elegantly (and efficiently) find and manipulate HTML elements with minimum lines of code.  jQuery supports this via a nice "selector" API that allows developers to query for HTML elements, and then apply "commands" to them.  One of the characteristics of jQuery commands is that they can be "chained" together - so that the result of one command can feed into another.  jQuery also includes a built-in set of animation APIs that can be used as commands.  The combination allows you to do some really cool things with only a few keystrokes.

For example, the below JavaScript uses jQuery to find all <div> elements within a page that have a CSS class of "product", and then animate them to slowly disappear:

As another example, the JavaScript below uses jQuery to find a specific <table> on the page with an id of "datagrid1", then retrieves every other <tr> row within the datagrid, and sets those <tr> elements to have a CSS class of "even" - which could be used to alternate the background color of each row:

[Note: both of these samples were adapted from code snippets in the excellent jQuery in Action book]

Providing the ability to perform selection and animation operations like above is something that a lot of developers have asked us to add to ASP.NET AJAX, and this support was something we listed as a proposed feature in the ASP.NET AJAX Roadmap we published a few months ago.  As the team started to investigate building it, though, they quickly realized that the jQuery support for these scenarios is already excellent, and that there is a huge ecosystem and community built up around it already.  The jQuery library also works well on the same page with ASP.NET AJAX and the ASP.NET AJAX Control Toolkit.

Rather than duplicate functionality, we thought, wouldn't it be great to just use jQuery as-is, and add it as a standard, supported, library in VS/ASP.NET, and then focus our energy building new features that took advantage of it?  We sent mail the jQuery team to gauge their interest in this, and quickly heard back that they thought that it sounded like an interesting idea too.

Supporting jQuery

I'm excited today to announce that Microsoft will be shipping jQuery with Visual Studio going forward.  We will distribute the jQuery JavaScript library as-is, and will not be forking or changing the source from the main jQuery branch.  The files will continue to use and ship under the existing jQuery MIT license.

We will also distribute intellisense-annotated versions that provide great Visual Studio intellisense and help-integration at design-time.  For example:

and with a chained command:

The jQuery intellisense annotation support will be available as a free web-download in a few weeks (and will work great with VS 2008 SP1 and the free Visual Web Developer 2008 Express SP1).  The new ASP.NET MVC download will also distribute it, and add the jQuery library by default to all new projects.

We will also extend Microsoft product support to jQuery beginning later this year, which will enable developers and enterprises to call and open jQuery support cases 24x7 with Microsoft PSS.

Going forward we'll use jQuery as one of the libraries used to implement higher-level controls in the ASP.NET AJAX Control Toolkit, as well as to implement new Ajax server-side helper methods for ASP.NET MVC.  New features we add to ASP.NET AJAX (like the new client template support) will be designed to integrate nicely with jQuery as well. 

We also plan to contribute tests, bug fixes, and patches back to the jQuery open source project.  These will all go through the standard jQuery patch review process.


We are really excited to be able to partner with the jQuery team on this.  jQuery is a fantastic library, and something we think can really benefit ASP.NET and ASP.NET AJAX developers.  We are looking forward to having it work great with Visual Studio and ASP.NET, and to help bring it to an even larger set of developers.

For more details on today's announcement, please check out John Resig's post on the jQuery team blog.  Scott Hanselman is also about to post a nice tutorial that shows off integrating jQuery with ASP.NET AJAX (including the new client templating engine) as well as ADO.NET Data Services (which shipped in .NET 3.5 SP1 and was previously code-named "Astoria").

Hope this helps,



  • This is simply amazing! Thank you very much for doing this. We use ASP.NET and jQuery and pine for better jQuery IntelliSense support in VS. Wow... just wow!

  • Best news I've heard in months! Kudos to whoever made this happen.

  • About time! MS is moving in the right direction. The same kind of decision should have been with NHibernate with regard to EF. :(

  • This is really exciting. I never expected to see an open source library show up in a Microsoft product.

    Good choice.

    Chris Sutton

  • Wow. I never thought I would see this. This is the first open source project that was supported instead of dublicated by MS. Keep it up, you are on track now! :)

  • Top notch stuff, Can't say too much more about this apart from that it's fantastic news!

  • Great news, Scott! Things are moving in the right direction. Exciting times.

  • What are you doing to get around the existing conflict of both the MS Ajax library and jQuery using $ as shorthand?

    This is absolutely fantastic news.

  • Awesome! As Chad says, AMAZING. I can't believe what I am reading. MS is going to use an existing unmodified oss project! I am speechless. Scott, given where the .net community was 3 years ago, the work you have done to help bolster a more open and cooperative .Net community lead by Microsoft is unprecedented. I hope we can continue to see more announcements like this and continue see more open projects like Ironruby and Asp.Net MVC coming out Redmond.

  • Wow...this is huge... Kudos for both, jQuery & Microsoft. Life (of the developers) will be a little better. :)

  • This is just what I needed.

    And I'm very excited that it's going to happen.

    Thank you!

  • I have to be honest. I did a date check vs. April 1 in my head before I finished reading this post.

    Wow, this is FANTASTIC news! I can't wait to tell the guys on the homepage team about this. :)

  • Scott,

    I think this is just such incredibly good news for ASP.NET developers. I'm posting from the jQuery conference in Boston and I can tell you that this announcement is making all the ASP.NET folks here super happy today.


  • This sounds like great news. Ordinarily, I would have been extatic. I was but it lasted about 5 min. Then, I remembered history.
    But just so we are clear: You are committing to us that MSFT will not "be forking or changing the source from the main jQuery branch" and you will "go through the standard jQuery patch review process" for tests, bug fixes and patches.
    As you can see, jQuery just managed to restore sanity to the browser DOM madness introduced by none other than Microsoft. We don't want this move to transform into "how jQuery became browser specific again".
    Remember T-SQL, Java, Mozilla (IE)

  • This is REALLY GREAT move!
    Big thanks for all who made this tandem real

    and WOW =)

  • Very exciting times indeed. I'm simultaneously ecstatic and relieved to see this shift to "openness" from MS, and thank you and all others that are making it happen. Keep it up!

  • I'm really impressed that Microsoft pursued this course.

  • good work Scott - this is the microsoft we need!

  • F**king Excellent news! Good to see Microsoft adapting to the community and moving towards a standard web!

  • Jquery have deserved to be recognized among top players =)

  • This is first example that Microsoft respected open source solutions and created partnership with them, hope the trend goes on.
    Scott, Please pick more tools and practices from Alt .net space too.

  • This is great Scott! jQuery is great...I've been using it for a while now and have wished that it was more integrated into asp.net ajax. Your team has obviously been busy. Thanks for making things easier on the dev community. BTW...Silverlight 2 can't come soon enough!

  • I'm curious to hear how Microsoft will address points of overlap between the ASP.NET AJAX Library and jQuery. In many way, jQuery is a natural complement to ASP.NET AJAX, providing Roadmap features such as CSS selectors. In other ways, it provides its own distinct methods for retreiving AJAX data, handling events and (with jQuery UI) extending controls. I see that you'll be integrating it with the AJAX Control Toolkit which I assume will address the overlap with jQuery UI - but what about other features? Will Microsoft support both? Deprecate the existing ASP.NET AJAX approach? Or will you allow both, but encourage the Microsoft methods?

  • This is a great addition to ASP.NET!

  • Great news, good to see MS recognising some of the existing work out there.

  • Now convince the IE team to use WebKit or Mozilla as their rendering engine and Microsoft will have finally be caught up to everyone else. Shocking decision, great job.

  • Interesting. I'm just curious how Microsoft will position it against current Microsoft Ajax library? Hanselman said that it will be complementary but, I think there are a lot of similar functionalities that are implemented differently between the two. Will Microsoft recommend to use either one for some specific scenario? or just up to the reader to select it?

  • A great decision. I suppose it's not a huge risk, say on the selectors front, as that may come to HTML 5 any way. But as I use jQuery for all current client side work, it is a very welcome piece of news.

  • I never thought I would see the day, this is so freaking awesome!

  • Good , But we still not familiar with Microsoft Ajax library :) , also adding more libraries will add more JavaScript files to the website ,because if i want to use the calendar extender with some jQuery stuff, i need to include Microsoft Ajax library and calendar script files and now jQuery scripts !

  • Happy Happy Joy Joy - or yippee!

    This is best news I've heard in awhile - and from my experience: it works great with asp.net mvc :)

  • Best news this year

  • WOW! I like this openness more and more... keep it up.

  • Wow. This is a really exciting announcement. Maybe I'll finally be able to persuade my co-workers to use jQuery!

  • Great news, and a good choice. Also good to see that Microsoft is not afraid to include open source software in its product. That wasn't always the case, and I wonder how hard this was to sell internally, is the legal team feeling alright?

    One thing though, jQuery is a moving target, it releases more often than Visual Studio. Will Microsoft provide up to date annotated versions?


  • This is fantastic!

  • Wow...I mean WOW!!
    I really really like the way MS is going about the dev divission of late. Instead of being the dark empire, you're getting the community involved. When I first saw the roadmap, I thought..."Hang on - a lot of it is what jquery does. Why are they replicating a lot of things? Knowing MS, you'd think MS would just 'buy' jquery. Still, it's a positive move...at least I can code in a manner I really like." Now, instead of buying, you're joining the jquery effort - making it even better for asp.net devs. This plays so nicely with the ecosystem. I can't imagine any better way you could've played this. Awesome. Well done. Bravo. Thanks you...Really...can't say it enough.

    Now...what does that mean for asp.net MVC and AJAX? Is jquery now the "official" way to do AJAX? One thing I'd really like to see is ModelBinders working with AJAX...I haven't tried it yet, (still eagerly waiting for your Guness' much awaited post - on Sunday?) and client templates look a good way to achieve it. Just wondering if there's a way model binders would work for AJAX just the way they do for full postbacks (or "POST" requests to the page to be a purist ;)...

  • This is one the greatest news I have heard from Microsoft side since long time. I and my developers, we are big fans of JQuery. It will be great to see it in action, with more widgets, plugins and official support. Great choice Microsoft!

  • Very very GOOD Notice.
    A next step: John Resig working in Microsoft team.


  • Simply - AWESOME. Next on the list - mbunit? moq? Ninject?

  • Great news! However, why lock in with jquery? In particular, will there be support for the just as largely used Prototype or others?

    Will this cause any issue with the use of other libs like Prototype?

  • I am so glad you guys are doing this. When MS insists on writing everything themselves, we miss out on all the cool stuff that is taking place in the web development community, we have to wait longer for it and when it comes it's YAATODW (Yet another api to deal with). So please keep this up :)

  • (picks self up from floor).
    Awesome, His Guness, just awesome.

  • This is so cool. Awesome work.

  • WOW excellent news for everyone!!! This is huge and most appreciated!

  • this is the best, jQuery is my favorite javascript framework, great work

  • Wow, I'm very impressed.

    Does this mean the VS team is interested in integrating other best of breed products such as NUnit, NANT, CruiseControl.NET?

  • Thank you for partnering with an open source project like JQuery. This is GREAT news! I hope the trend continues at Microsoft.

  • This is interesting. I wonder if other teams at Microsoft will follow-suit and embrace third party tools and libraries as opposed to building something from scratch on their own. Most of the time the teams seem to be afraid of singling out a particular produt over another and would rather build their own, which can often be less feature-rich.

    This open-mindedness really helps the developer community flurish and things just happen much quicker.

    Kudos to you and your teams on such a bold and unexpected move.



  • We are using jQuery, I like jQuery. This's a very great news for me.

  • I'm skeptical... the MIT license makes it very easy for MS to "embrace, extend, and extinguish" jquery as we all know and love it. For example, I see the progression as follows:
    1) MS promises to stick with stock jquery and submit patches as everyone else
    2) MS says that jquery isn't accepting their patches fast enough, so they need to maintain a slightly modified branch (hmm, perhaps for Intellisense?)
    3) Time passes... MS's patches make their version of jquery slowly grow apart form the "real" jquery
    4) "Accidentally" MS jquery has a few bugs in non-IE browsers. MS promises to fix it in the next release - which ends up being delayed again and again... so non-IE users are left out in the cold.
    5) The jquery lib is "compressed" for speed (of course), and everyone accepts this... effectively making the source code much harder to read/access
    6) The download link for the source "accidentally" breaks... repeatedly.
    7) End state! jquery has been branched by MS, the source has been closed (completely legally), the original community decimated, and jquery only works on IE. And all the while, MS looks good for having used and supported "open source" software.

    "So this is how liberty dies, to the sound of thunderous applause"

  • This is outstanding news. It's great to see Microsoft embracing such an excellent framework rather that trying to reinvent the wheel. It's also great to see you wont be branching jQuery - Embrace without the Extend! I second your opinion on the book "jQuery in Action", unquestionably the required read on this subject.


  • This is very good news.

    I'm using jQuery and put my own intellisense support into the latest version (in a few minutes using a diff tool). Results are not as good as I'd like, so I'm delighted to see that you are going to release something better.

  • Sweet. To bad you guys didn't do this with NHibernate rather than spending all that time and resources to develop two separate OR/M libraries. Sigh.


  • very happy to hear this news.

  • This is really GREAT NEWS.
    Congrats for the decision.

  • This is REALLY awesome! Thanks for embracing such an awesome framework!

  • This is simply exciting stuff...

  • Great News .. hope Microsoft will continue to add more tools and libraries like(jQuery) in near future.

  • that's gr8...

    this is what the web developers want.

  • Well, in addition to whay Graig said, I'm afraid of jQuery colliding with other js framework you might be using, as it is my case.
    We develop asp.net ajax applications with mootools, so i hope i'll be able to "swith off" jquery and still use mootools framework with its $ command and more...

  • Great news and smart decision by Microsoft. Why try to reinvent such an excellent and superior framework. I'm looking forward to using the jQuery intellisense.

  • OMG! This is like the most bewilderingly amazingly stupendious news i've heard in 2008. F'ing fantastic.

  • Wow, this has to be one of the best things to come out on ASP.NEY yet. I've been playing with the various Javascript libraries, including Prototype, but to have a ASP.NET designed to work with a standard library is fantastic news.

  • It is really great idea!

  • Glad you chose jQuery - scriptaculous doesn't usually play nice with .NET and other third-party controls. Will it be jQuery as-is, or jQuery plus some helper functions? Most importantly, something that allows us to access elements by the ClientID, instead of having to view source and find out what the .NET-mangled ID is for any runat=server tags?

  • Did someone bring Christmas forward?

    I've been moving away from MS for some time now because they always seem to want to 'roll their own' xyz technologies when there are usually plenty of well supported open source solutions out there, jQuery being a classic example and a library I already use with VS, so this is very welcome news.

  • You are my heroes. Congratulations for resisting the greatest temptation for every open source project - forking. In my opinion forking is what holds open source back. I hope you stay on that position in the future.

  • One tiny step in the right direction. Now all we need is for the IE-group to switch renderer to Webkit or Gecko!

  • Hi, this sounds great but i have a few questions:

    1. Will the jquery library automatically get added to the page when we place a script manager on the page?
    2. Where will the library be hosted? would this point to a third party place? Google hosts the jquery library which keeps the same library in the browser cache across all sites that utilize it. It would be great to see microsoft do the same with both jquery and asp.net ajax. Maybe a property on the script manager would give the user an option of doing this.
    3. If microsoft is going to utilize the features of jquery in asp.net ajax then will some of the balk of asp.net ajax be removed or changed to call the jquery alternatives (to be backwards compatible), ie things like $get(...) to $(...) and Sys.Net.WebserviceProxy.invode(...) to $.ajax(...) etc.
    4. How are you going to handle support for different versions of the library within visual studio.
    5. Are we still going to be building asp.net ajax server controls in the same way? I prefer this method over jquery plugins.
    6. What will happen to some of the duplicated stuff in the ajax control toolkit? For example the animation extender.

    I like the way the asp.net ajax library is going. By utilizing the features of jquery and with the proposed features (client templates, client dataview control) and some of the existing features it all compliments each other really well and can be very powerful.

  • I love this. Hey devs, let's enjoy the ride!

  • awsome news, thanks to everyone who made this happen :-)

  • Hei, that's amazing news! Congratulations on this excellent decision! jQuery is really great and that combined with ASP.NET (especially MVC) is marvelous.

  • Freakin aweseome! Great move. Focus on your bits, and accept the community standards.

  • Great news, but what about JQuery UI? Is that officially a separate library, so it won't be included, or do you see it as part of JQuery and you will be including it?

    JQuery UI is still fairly immature, but already overlaps quite a bit with some ASP.NET AJAX UI widgets, and will do so more and more as it develops. What plans does MS have, if any, for JQuery UI?

  • Excellent news! This is another reason why Scott should be put in charge at Microsoft. With the new MVC work and the change in direction for developing new technologies while respecting standards you guys are doing a great job. Please can we never go back to the old ways of new product development, acting like a 10 tonne gorilla with a blind fold on stomping all over good practice.

  • its interesting to .net devs that jQuery will be tied to vs.net. Great news and I will enjoy looking forward

  • You have no idea how much easier this makes JQuery to sell to my clients. Having MS backing without MS ownership is an awesome solution.

  • This is really exciting! I can't wait to tryout the download in a few weeks!

  • This is simply fantastic news. Our team were already making extensive use of jQuery along side MVC in our latest project. This news confirms that we were on the right track. Thanks Scott G and the rest of the MS groups responsible for OK'ing this decision. It was the right thing to do and the entire web development community as a whole will only benefit from this.

  • I hope MS wont touch the source ;)

  • This is the best thing MSFT could do for their ASP AJAX!
    jQuery rocks and has been great to use with PHP, but
    with MSFT adopting it, it's going to skyrocket the web,
    Even more than it already has in the Open Source Community!
    Great job MSFT!

  • Hello Scott,
    I really found jQuery great for few very small tasks. I hope there can be a new section in "Learn" of ASP.Net web site for using jQuery with ASP.Net. May be some videos and some tutorials. Please do remember that still there are so many people using VS 2005 and ASP.Net 2.0.
    May be you can keep this section open for all, like I have developed something with jQuery and I can submit it there.

  • This is simply put the best decision you could've made for ASP.NET MVC. Hopefully this will also mark the end of the me-too-thinking inside Microsoft (ADO.NET EF vs. NHibernate, VS unit tests vs. NUnit, oh-my...).

  • Great news! I've been using jQuery and ASP.net unsupported for a while now.

  • I'm not really an HTML guy...but when I see this JQuery it immediately reminds me of LINQ...a good thing.

  • Mr Guthrie, I could kiss you.

    Thank you!

  • Great, since most of us use jQuery (or some other lib) there is little to no major impact. jQuery will be part of VS...for those who don't use it today. Wait...don't use jQuery..thats right those who don't know JS.

    It's a good first step but to bring quantitative adoption MS will have first create components for those non-JavaScript..er Jscript..knowing developers can use. And it would be nice to stop the obstruction madness...

    I still find it crazy that on todays AJAX web I can work with so many "web developers" who can't write a lick of JS....

  • To Thumbs Up. Great Move Microsoft!

  • This is great , and smart news. Congratulations and thank you!

  • This really is incredible - All you doom and gloom people need to hush now and just see this as another step in a different Microsoft.

    Scott, you're really making this shift happen and the community is going to sing songs of your heroic many years from now (actually, I doubt anyone is going to be singing, but you get what I mean...)

  • This is great and all.... but a couple of concerns I would have right away are that.... the current MS client JS framework is already pretty heavy adding another framework library like jQuery is going to add even more bloat to the existing framework. So page / control developers who will leverage the controls from the ms ajax toolkit today and some of the new controls which will leverage jQuery will blindly have huge client payloads as the need for multiple libraries will become transparent.

  • Excellent news. This will definitely be a great help to the .Net community.

  • Scott, you rock! I started using jQuery 1.2.x recently with asp.net 2.0 web apps and it was a real challenge at first but now i love it and get great feedback from users. Still using the basics and even so, still primitively but getting better. BTW, I tried the other js frameworks out there, but found jQuery the easier to use.

  • Apologies if this has been asked -- probably many times already. Can you comment on when we can expect an official release from Microsoft that includes jQuery and/or patch for Visual Studio to include it? If the timing is a long way out, should we go ahead and start manually integrating jQuery into our apps? What will be the mechanism for including the scripts (through built-in ScriptManager support of some type or just as an external include)? Thanks.

  • With jQuery shipped with ASP.NET MVC, I think MS is going to the right direction in terms of building web apps. Looking forward to see similar initiatives ... I mean, instead of producing their own, I believe they should support other open source projects and add on top of them for specific features they want. I have in mind, LINQ & ENTITY FRAMEWORK VS. NHIBERNATE AND HQL. I would have been nice for them to support it instead of creating their own ... Just my 2 cents ...

  • Good news, notice that we already have an excellent intellisense support for jQuery in Aptana Studio, a great IDE for web projects.

  • Hello ScottGu,

    I would like to see the same roadmap sounds about Client Data and Server Data for Silverlight and ClickOnce App.

    Could I Dream about it?

    Thank You!

  • This is amazing, best news ever, I love you Scott.

  • Hi Scott,

    How will updates to the jQuery library be handled? Will periodic hotfixes be released when jQuery changes versions or a new patch is included?

  • Really like Microsoft opening up to open source. Makes being a developer on the MS platform much easier and fun!

  • Another very good move for ASP.NET land! Great to see :-)

  • This is outstanding to see MS finally understand the value of integrating with good open source projects. It's a huge win for MS and more importantly developers and end users. Please expand extend this thinking company-wide.

    Actions like this will bring MS far more value than the $300m ad campaign.

  • Well, I'm not a big fan of jquery, but I am excited about the shift in policy at Microsoft.

  • Great news. Bye, bye aptana studio.

  • I am using jQuery in few ASP .NET websites and on a SharePoint Intranet at work so it is a very good news :D Thanks a lot Scott !!!

  • Great news! Finally Microsoft is shaking off the "not invented here" syndrome.

  • No way! Glad to see that you guys at Microsoft have seen the jQuery light. It is the way forward for sure. To be honest, I have been losing touch with ASP.NET, it seems so clunky at times. When I discovered jQuery I realised that I could introduce a fresh zest to my websites. I think this is a great step forward and the combination of ASP.NET MVC and jQuery could be a superb partnership.

    All we need now is a better framework for developing single page applications and I think this will be the next major step forward.

    Good Work Guys

    The Dannster

  • Excelent move Microsoft!

  • Excelent move Microsoft!
    JQuery rocks.

  • great News....

  • Super. This is someting that was lacking for years.

  • Microsoft has no choice other than adopting jQuery. jQuery is so powerful that Asp.Net AJAX library is not even closer to that. That is a good decision u guys have made.

  • Excellent news!
    Greatings from Sweden

  • Great new? WTF, hell I could care less if MS supports JQuery, I use it instead of their fat slow MS Ajax framwork anyway. I fail to see how this is meaningful news other than MS tooting their horn to show they support Open Source (not). I don't need MS approval or support to use JQuery today! So whats so Cool about this?????

  • Ahhhh so it was Microsoft joining with and OS team that cuased the credit crunch. ;)

  • I am having some concerns about so much logic being pushed in to the view which historically for testing purposes should remain as dumb as possible. The JQuery syntax in particular makes it hard to write unit tests in Jsunit. It took me awhile to really get my head around the whole TDD approach which if I had to boil it down to one line of description would be that "we fake the input for the object we are testing." Jquery's very nature, at least in the way that Jquery developer's write there code is not very testable. If you are to write functions as opposed to using selectors to call an element in the html you can begin to fake inputs and so forth. The problem with this approach is that we then loose the advantages of Jquery which are that you can lay any script on top of any html so long as you reference the different classes and selectors in the html in your script. If this is not clear let me write an example here:

    $('#myElement').val('some test code');

    This is my mind is not a testable statement. Unless we mock the html that populates the this element. Which can be done and would definitely test this line of code. However, what the real problem is that we run into all kinds of runtime issues due to element names changing so what I really want to do is to test the relationship between the Jquery and the real html. This is what i am trying to work out in my head. If we can't do this we are just adding complexity that we can't test and probably encouraging a lot of bad design. Thoughts|Comments?

  • This is excellent news!

  • Will wonders never cease , Way to go !

  • This is absolutely AWESOME!

  • Gu explains jQuery will be integrated with Visual Studio while clintonG tries to get his attention explaining Nate Koechley [natek AT yahoo-inc.com] authored the YUI Grids. Nate may be consulted regarding the integration of the YUI CSS library with Visual Studio.

    He and his pals at Yahoo! did an amazing job with the JavaScript in their Yahoo! User Interface library (YUI) but its really their YUI CSS library that is to CSS libraries what jQuery has become to JavaScript libraries.

    I mean since we're all of a sudden being all grown up about this for a change its time to accept the fact that all of that "friendly" CSS hype was not and is still not so friendly after all; a nice try but an abject failure so far off the mark it remains stupifying attempting to cope without the YUI CSS library.

    So we must not forget the other aspect of UI development; CSS. Its clintonG that hopes Gu will agree to make it possible to integrate YUI CSS with Visual Studio given the same effort that is being expended to support the use of jQuery.

    In my world view we'll then have the best of breed; C#, jQuery and YUI CSS libraries integrated into a framework that for all intents and purposes has become seamlessly agnostic with nothing to prove except being used to produce the hightest quality results which speak for themselves, however...there remains unfinished work; comparable XSLT, XML and XSD libraries.

  • how is jQuery compared with scriptaculous?

  • Where I find an exemple of jQuery with asp.net 3.5?

  • thank's for the great news. really exited.

  • wow!
    this is the 2nd dream come true since silverlight :D
    I can't tell how much I hated javascript before jQuery. since than, I really enjoy using it.

  • As a .Net developer I'm feeling less discriminated by FOSS community now.
    I'm brazilian, and when I say that I'm a .Net developer, everyone looks at me as suspicious. Anyway, we get used in the long of the time. :(

    What's the next step? Releasing the .Net 3.5 extensions as open source? This would be great for Mono. To dream doesn't cost anything.

    Thank you Scott.

  • just fantastic..really exited.

  • I am amazed. It is really great to see Microsoft embrace a technology instead of treating it as competitor and trying to imitate it.

  • : ) ) yeaaah... This is very good...

  • It is great, that Visual Studio have jQuery intellisense.

  • Scott, we have been using jQuery for some time now and have found the jqGrid to be a very productive way to display grid data in our MVC apps. Since with jqGrid you only have two lines of HTML, one for the grid itself and one for the pager, with pages that have multiple grids, up to over 10 grids in some pages, the ajax architecture that the jqGrid supports is a great performance booster. However, there are still some issues here and there with the jqGrid plugin specifically, will your team be supporting/helping with the jqGrid, or any other extensions/plugins or only concentrate on the jQuery core library? Also, how will you support it, by simply shipping with VS of actually throwing some resources at it also?

  • This is absolutely fantastic. Couldn't be more impressed than I am with Microsoft deciding to embrace the open source market more and more!


  • This is pretty amazing, I use jQuery in an existing AJAX app and knowing the library will be both more tightly coupled as well as officially supported is great news!

  • I love Microsoft and ASP.NET even more for this!! Thanks for making our life easier.

  • I am so fantastically impressed! I am soooo glad to see this type of thought process and action coming from Microsoft. Please please please promote whomever conceived and approved of this idea.

  • cool ~~
    good news , thanks microsoft!!!

  • Any chance there will be some Visual Studio intellisense for Prototype at any time?

  • WOW!
    I've been now working with jQuery for the past 1 1/2 years and always have wondered when the big show will finally notice them. Happy to read about that.

  • Great news, I'm using a lot of JQuery and Asp.net ajax in my project and I think that the partnership with JQuery team is great!

    Thank you very much!

  • It's very exciting to know that this is happening. We were early adopters of both jquery and the asp.net platform and having jquery tightly integrated with Visual Studio, native jquery-based widgets and more people contributing to the already awesome jQuery plugin repository, core and jquery-ui is a really nice step forward. Having MS adopt an opensource project in this way is huge, too.

  • Absolutely amazing

  • sorry Scott for using this medium to consult a jQuery behaviour, but i haven't been able to find a resolution:
    can this html break jQuery ?
    &lt;input name="ctl00$body1$Tab_Customer1$txtAddr1" type="text" value="text value" id="ctl00_body1_Tab_Customer1_txtAddr1" class="field-data" /&gt;
    (its an asp:textbox inside a usercontro, inside a panel, inside a contentholder)

  • I have not checked on this, but my company may not permit the use of jQuery even though it is under the MIT license. (Licensing can be tricky.)

    If, hypothetically, I cannot use jQuery, is that going to cause issues using ASP.NET and ASP.NET AJAX going forward?

    Stated another way: How much will ASP.NET depend on jQuery going forward? Will it be absolutely dependent (probably not)? How much new functionality would I miss without jQuery?


  • Hi Peter,

    >>>>>>>If, hypothetically, I cannot use jQuery, is that going to cause issues using ASP.NET and ASP.NET AJAX going forward?

    ASP.NET and the core ASP.NET AJAX features will work fine without requiring jQuery. So you will still be ok even if you can't/don't use jQuery.

    Hope this helps,


  • Linux, Gnu, Unix..

  • The best and most important thing in the jQuery is that it supports numbers of selectors (event a subset of XPath query!), and allows to apply same operation to all results.
    Mozilla Firefox provides jQuery out-of-the-box - it is included into the browser.

  • Everybody should learn jQuery. It makes UI development much more easy.

Comments have been disabled for this content.