These annotated "-vsdoc.js" files can include XML comments that provide help documentation for Java Script methods, as well as additional code intellisense hints for dynamic Java Script signatures that cannot automatically be inferred. You can download both j Query and the j Query-vsdoc file from the official download page on the j site: Save the file next to your file in your project (and make sure its naming prefix matches the jquery file name): You can then reference the standard jquery file with an html comment at the top of a standalone file.When you do this VS will now look for a file in the same directory as the script file you are referencing, and if found will use it for help and intellisense.At first I thought this behavior was due to the new "suggestion mode" in Intellisense, but no amount of toggling with CTRL ALT SPACE would bring back the auto-complete behavior.
Rick Strahl also has a really nice Introduction to j Query article that talks about using j Query with ASP. Karl Seguin has two nice j Query primer posts here and here that provide shorter overviews of some of the basics of how to use j Query.
I also highly recommend the j Query in Action book.
The problem of course when you do this is that by default VS has no way of knowing that this script is available within the user control - and so won't provide intellisense of it for you.
One way you can enable this is by adding the tag and provide intellisense for it within the user-control.
As a previous poster suggested, disable intellisense (and chose a potential alternative -- I also support VAX).
Supposedly the hotfix and SP1 provided by MS will fix intellisense problems, but not all. You are better off to disable it and rely on something else.
This hotfix also includes the ability to control Intellisense via Macros. As for making SP1 more friendly for existing code, you might also check out this hotfix for template compilation: Rename "C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages\feacp.dll" to something else (like "feacp.bak") to disable Intellisense. When it works, it's great, but more often than not it will cause more problems than it's worth.
I recommend getting Visual Assist X to make up for it (it also has a number of other useful features as well). It will hang up, it will parse through files while you are trying to compile code and will generally make VC 2005 sometimes run like a dog.
Rick Strahl also has a good post about using j Query intellisense here.