What's new is that the parsing doesn't fail and because of it doesn't break parsing of other JavaScript files.
If you don't do anything and leave jQuery.js as is you only get some limited supoport. While I don't think I'd want to add VS specific comments to all of jQuery's functions and keep up with it for each of the frequent new releases of jQuery, I think adding a single single comment to the main jQuery function itself is probably worth it and it provides a pretty good payback for little effort.
VISUAL STUDIO JAVASCRIPT INTELLISENSE HOW TO
Jeff shows a small example of how to fix up jQuery functions by adding Visual Studio documentation with a suggestion of marking up the full jQuery library.
VISUAL STUDIO JAVASCRIPT INTELLISENSE CODE
The hotfix apparently works around the problem parsing jQuery and so you can get some Intellisense out of the box and with a wee bit of marking up the jQuery code you can now get some pretty useful Intellisense from jQuery in the JavaScript and ASP.NET Html editor. The problem is that jQuery is basically one big function and since it failed to parse - you got nothing. Previously working with jQuery got you - well, nothing because the the Intellisense parser didn't properly parse the jQuery source file and so failed to produce any Intellisense for anything in the jQuery library. Jeff's post talks about how you can make Visual Studio's JavaScript Intellisense work better with jQuery. Jeff King, who's one of the program managers in the Web Tool Division and who focuses on the JavaScript editor, has posted about another byproduct of the Visual Studio hotfix I mentioned a few days ago.
0 kommentar(er)
