Suddenly, like magic, everything works again. All we need to do is make sure it is included in the project. There is no need to reference this file anywhere. This new information is provided by the TypeScript language service, which uses static analysis behind the scenes to better understand your code. Starting in Visual Studio 2017, JavaScript IntelliSense displays a lot more information on parameter and member lists. We can modify our gulp file to also output a non-minified version of the combined CSS file and include that in our project. What's new in the JavaScript language service in Visual Studio 2017.
![visual studio javascript intellisense comments visual studio javascript intellisense comments](https://i.stack.imgur.com/qg8H1.png)
Unfortunately Visual Studio seems to ignore any minified CSS files! This seems very strange to me but at least there is an easy solution. So what’s up with CSS? Why isn’t CSS Intellisense working? According to Microsoft, VS 2013 is supposed to inspect any CSS included in your project and make classes from those CSS files available via Intellisense in the HTML editor. Even though our project only includes a couple combined and minified JS files, everything still works exactly as expected. As such, jQuery intellisense works just as it did when referencing the packages from Nuget. With Autosync enabled by default, the included files are automatically added to the _references.js file. On my work machine, if I type /// Visual Studio automatically generates the XML that I need to comment, but on my personal machine, its not working.
/Visual studio handles this nicely with the example in the article. I am currently documenting a JavaScript project with Visual Studio compatible XML intellisense comments.
#Visual studio javascript intellisense comments code#
Many developers already enjoy its power when code JavaScript. One of the most useful features of the Visual Studio 2008 and Visual Studio 2010 is JavaScript IntelliSense that allows developers write JavaScript code faster, with fewer errors and reduce learning time of some JavaScript frameworks. Intellisense for JavaScript files is handled by the _references.js file. Leveraging Visual Studio JavaScript IntelliSense. Let’s dig into this a little deeper then… JavaScript Intellisense This was especially puzzling because it appears that JavaScript intellisense was in-tact.
![visual studio javascript intellisense comments visual studio javascript intellisense comments](https://i.stack.imgur.com/f08HT.png)
I was not getting any CSS intellisense for the Bootstrap classes. So I set out to investigate this and sure enough I was also seeing the same problem on my machine. He noticed that after using this approach, Visual Studio was no longer giving him the expected Intellisense for Bootstrap CSS classes. One reader asked me how this approach affected Intellisense for the referenced package. As I outlined in my previous blog post, I have recently started including client side (CSS / JavaScript) packages via Bower and Gulp instead of Nuget.