This fix will be available in the next service pack (no date announced yet).
In the meanwhile, there’s actually a simple workaround.
If you didn’t have the time, you could download such a file from friendly members of the community such as James and Brennan.
If you have a large script or slower machine, it may make sense to increase the timeout limit. Note, if you use jquery-1.2.6js, you may need to rename the file to match the search pattern. One unique benefit of the file we have released is that it supports and understands j Query plug-ins. …you would see “myplugin” show up in Intelli Sense. We’ve noticed a few plug-ins do not work, and commonly this is because there is an Intelli Sense incompatibility issue with the plug-in itself (as opposed to the j Query documentation file). Jeff King Program Manager Visual Studio Web Tools . He has also written two EBooks 51 Recipes using j Query with ASP. I had recently posted about the j Query 1.4.1 Intellisense support for Visual Studio.If you’re in a Java Script file, use the normal file reference syntax to refer to the “vsdoc” file.There’s no need for tricks here since this comment is only meaningful to Intelli Sense. The ideal user experience should be one where you do not need special tricks as mentioned above.A user commented back saying that intellisense did not work for him.He encountered an error in Visual Studio that said “Error updating JScript Intelli Sense”If you are trying out the j Query intellisense for Visual Studio and encounter the error “Error updating JScript Intelli Sense: Object doesn't support this property”, then make sure that you've installed the hotfix that adds JScript Editor support for “-vsdoc.js” Intelli Sense documentation files. Once you have applied this hotfix, you should be able to use intellisense for j Query 1.4.1 as shown below.At runtime the if (false) statement will ensure it this documentation file is not rendered (and executed) as script.This trick allows the “switching” behavior you want.