Making the most out of JavaScript Intellisense in VS2012

Intellisense for JavaScript has always felt to me like an unfinished addition to Visual Studio, something that promises so much but doesn't deliver for larger projects. Manually adding and then maintaining another set of dependency references just for Intellisense has just never seemed worth it. However, with the launch of Visual Studio 2012 Intellisense has had a refresh, does this mean it's now worth another look?

In this post I've taken Colin Eberhardt's HTML5 Property Finder app and enhanced it with AMD (Asynchronous Module Definitions) allowing each JavaScript file to define it's own dependencies, much like C#. This one source of dependency data is then used when writing the code to automatically provide Intellisense, during debugging in the browser to load each JavaScript file in the correct order (no more long lists of script tags!) and when releasing to build a single optimised JavaScript file.

Read the full article on Code Project

MORE BY CHRIS

blog comments powered by Disqus