The Wayback Machine - https://web.archive.org/web/20240611200750/https://github.com/Microsoft/nodejstools/issues/1147
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

NTVS 1.2 Feedback #1147

Closed
mousetraps opened this issue Jul 18, 2016 · 8 comments
Closed

NTVS 1.2 Feedback #1147

mousetraps opened this issue Jul 18, 2016 · 8 comments
Labels

Comments

@mousetraps
Copy link
Contributor

mousetraps commented Jul 18, 2016

Love it? Hate it? Let us know what you think!

@mjbvz mjbvz added the feedback label Jul 28, 2016
This was referenced Jul 28, 2016
@mirumatsu
Copy link

mirumatsu commented Aug 1, 2016

Had this weird problem. I'm on VS 2015 Community with NTVS 1.1 installed. Everything just works fine.

Then saw that 1.2 has been released, so went to upgrade.

But when i tried saving .ts files it says on the status bar "The project contained errors. Output generation skipped". But it works whenever I Build the project.

So I decided to go back to 1.1 for the mean time.

@benquarmby
Copy link

benquarmby commented Aug 2, 2016

The editing experience in 1.2 is much faster and closer to what I've come to expect from browser based JavaScript in Visual Studio.

Unfortunately with issues like #1185 and #1188 it's still not stable enough to recommend and roll out across all our teams.

@mjbvz
Copy link
Contributor

mjbvz commented Aug 4, 2016

@mirumatsu Can you share the full error message you are seeing and any other details, along with some steps to reproduce the issue so we can look into fixing this? Does it happen for new typescript projects as well?

Thanks.

@mirumatsu
Copy link

mirumatsu commented Aug 9, 2016

There were no error messages, not even a line. No error when building.

I created a new TS project, and just copied the files from the other project to check if the error would still be there. And, yes, the error still occurred.

This was my setup on my home PC

  1. Installed VS Community 2015
    Installed NTVS 1.1 after 2015
  2. Updated VS [Update 1]
  3. Updated VS [VS with Update 2]
    Updated NTVS 1.2 RC
  4. Updated VS [Update 3]
    Updated NTVS 1.2

Then the problem started with last setup.
Then I decided to go back to previous setup, but the error indication was still there.
Made a full uninstall, then reinstalled with setup 3, but still there.

My last attempt was:
5. Full reset of my PC
Installed VS Community 2015 with Update 3
Installed NTVS 1.1

Pulled the project from office PC.
Saved a file, Built the project and Error indication gone!

But I noticed something regarding node tools analyzing my codes (never showed before),
so I opened my project folder and noticed that ".ntvs_analysis.dat" was there (never there before).

Suspicion: .ntvs_analysis.dat's absence is the culprit.

@mjbvz
Copy link
Contributor

mjbvz commented Aug 9, 2016

@mirumatsu Just confirming that you are on NTVS 1.2.

The .ntvs_analysis.dat file is only used by our old static analysis engine that powers intellisense. You can see which intellisense engine you are using by going to Tools -> Options and then Text Editor -> Node.js -> Intellisense. You should be in ES6 IntelliSense. If you are already on ES6 IntelliSense, the .ntvs_analysis.dat file will not be used at all. It was probably created if you opened the project with NTVS 1.1.

@mirumatsu
Copy link

Currently I'm on NTVS 1.1 ancd my default IntelliSense is Full IntelliSense. I see the ES6 IntelliSense Preview as the last option. I'm planning to give 1.2 another try. Is the ES6 IntelliSense in 1.2 still a Preview or is it like a final build?

@mjbvz
Copy link
Contributor

mjbvz commented Aug 10, 2016

@mirumatsu With NTVS 1.2, ES6 IntelliSense is the default option that we want all users to be on, except if they absolutely cannot live without a certain ES5 IntelliSense feature that is no longer supported. The new IntelliSense is a better overall experience and much more stable as well.

@paulvanbrenk
Copy link
Contributor

Released several versions since 1.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants