Out of the box we get basic intellisense for what the editor can determine on its own about the Java Script code.

The Intellisense file and the hotfix in combination are a welcome addition to Visual Studio – it makes working with j Query inside of the VS Javascript editor a lot easier because the documentation provided through the Intellisense interface is pretty rich and helpful in many situations. Although j Query is specifically targeted here – this mechanism works with any file, so if you want to create Intellisense script for your own javascript files you can also store them externally.

The downside is that maintaining comments in an external javascript code file is pretty much a maintenance nightmare – Intellisense currently needs to have a running Javascript file in order to interpret the comments.

So then when referencing the file I’d get the same Intellisense.

With this support provided in Visual Studio it’s now become a lot easier to provide documentation in an external file simply by having a –file for the same file.

Visual Studio Code provides excellent intellisense for Java Script, Type Script, and C#. NET 5 or node or client side code, you’ll see a new level of intellisense here. If you hover over a variable VSCode shows the signature of a function or the type of a variable, if it can be determined.

Follow this series to learn more about what you can do with Visual Studio Code!

In case you missed it: Microsoft released the second part of their support tools for j Query in Visual Studio this week.

The second part comes in the form of a hotfix for Visual Studio 2008 SP1 that provides built-in support for –files to – when present – automatically provide Intellisense support in Javascript documents.

A better solution for this is eventually needed or else some built in tools that can strip comments automatically.