1 – Create a “preload” file
This is a small script that sits in between loading jQuery and loading your page scripts. All it contains is the following statement:
var $j = jQuery.noConflict();
Save it as preload.js and you can then sandwich this in between loading the jQuery framework and loading the page scripts as so:
In your actual work scripts, you can then reference jQuery and the preload using the standard VS reference notation:
Visual studio will have sorted out it’s type resolution for $j meaning that so long as you also have the jQuery .vsdoc file in the same folder as jQuery you get this glorious view:
The pros of this technique are that you can drop in new versions of jQuery at a whim and not have to worry too much about having to update preload.js. Of course the downside is that preload.js then needs to be sent to the client, with all the associated overhead of a get request.
2 – Append noConflict onto jQuery
There are those that will believe that the jQuery file is sanctimonious and should never be tainted by a developer’s touch. As it is I’m already using ASP.NET and cursed for all eternity, so how much worse could it be? So path two is pretty straightforward, open up the jQuery and jQuery.vsdoc files and add var $j = jQuery.noConflict(); to the bottom of the file. Again, this will sort out all the resolution gubbins while you’re working away in your own scripts.
Just remember that if/when you update your original jQuery files to also replace the noConflict statement at the bottom.