Following from a previous post I once did on JQuery VSDoc Support within Visual Studio the main way of referencing this has changed inVisual Studio 2012. I thought I would do a follow up article as the online articles I have found have been not as easy to understand as possible.
Within the dialogue above you will see we have a couple of different types of references and depending on their you must configure them differently
I played around with a few different configurations on how to load these such as
- Putting the JQuery VSDoc on a mapped drive and adding a reference directly to the options
- Adding the reference relatively
I found that although adding the VSDoc to a mapped path or shared location would allow everyone in a team to simply add this to the options there was no way to differentiate versions and as different projects might have different versions it wouldn’t work. My suggestion is have a pre-set folder such as ScriptReferences in every project with a _references.js file in it and then add this as a relative path in the Visual Studio options. Then each project could add the versions it uses. If there was some way to cascade options on a project level like Resharper does you could do it the first way but I currently don’t know a way of doing that.