Unable to add global Intellisense JavaScript link in Visual Studio 2017 RC

I am trying to make the transition until 2017 from 2015 as painless as possible. The code base I'm working with has several custom libraries that I was able to add as links in VS 2015.

However, in VS 2017 RC, the β€œlinks” option was removed from the options-> text editor-> JavaScript / Typescript β†’ Intellisense menu, where it was present in VS 2015.

Any direction in this work is welcome.

Be healthy

+6
source share
3 answers

My understanding is that it uses the new Salsa JavaScript service.

This blog link (provided by i100) contains the following statement in the Known Changes section:

Another key difference is that while the old language service supports an extensibility model that allows you to customize extensions for specific third-party JavaScript libraries, Salsa no longer supports these extensions in favor of TypeScript definition files, which encourage collaborative collaboration and are easier to maintain relevance.

Although the wording is somewhat ambiguous for me, I assume that this means adding javaScript libraries as links is not directly supported in VS 2017. The only way to get Intellisense in VS 2017 is with a TypeScript definition file.

I found this question on how to generate TypeScript def files from existing JavaScript files. The usual wisdom is that TS def files require more specificity than JavaScript files, and therefore they are most reliably created manually. However, this may not be an acceptable solution if you are like me and have tens of thousands of lines of custom library definitions.

There are several programs that are said to automatically generate def files for TS files, but I have never used them and cannot talk about their effectiveness.

dts-gen is created by Microsoft.

The dts-generator is created by SitePen.

It seems that the industry believes TypeScript is the way of the future, and are working hard to make TS standard development standard.

+1
source

There are changes in the js engine in intellisense. You can get more information and samples here and here .

NTN

Ivo

+5
source

I don’t want to know what microsoft thinks, what will happen β€œin the future”, that they devour dust for a long time. VS2017 no longer supports pure js intellisense, and I don't want to learn a language that "compiles" in javascript.

towards the end, I uninstalled VS2017 and support VS2015 until I research something better.

0
source

Source: https://habr.com/ru/post/1015128/


All Articles