-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intellisense and Error Detection Not working in 1.6.0 #13640
Comments
I just shut down VSCode completely and opened a different .NET Core project that had no JS/Node/Typescript files and the same thing is happening. |
+1, javascript and angularjs intellisense stopped working. All my settings are gone too. |
Almost all the intellisenses stopped working for me on vscode 1.6 |
@djx339 could you open Help > Toggel Developer tools and see if there is anything in the console. |
@dijitalmunky Lets focus on C# here. I need more information understand this because the simple sample works for me. There is the dev console (F1 > Developer Tools) and also the OmniSharp output (View > Output > Omnisharp Log). Please attach check them for errors/warnings and report back |
@jrieken I also have the same issue. There is nothing suspicious in logs during the error disappearance so I've made a small screencast to show how it happens: https://www.dropbox.com/s/mlwm9wrjk49zu73/vscode.mov?dl=0 Version 1.6.0 (1.6.0) If you need more info just contact me. |
Can someone try to get a small reproducible sample and attach it here? I am trying with a simple 2 file repo but that doesn't work... |
@DustinCampbell does this ring a bell? do you see similar issues? |
I've received this issue over in the C# extension repo: dotnet/vscode-csharp#812. Since a few people have solved the problem by rolling back to VS Code 1.5.3, it's potentially related. Note that the C# extension hasn't shipped a release for a couple of sprints (~6 weeks), so there's no change to the extension. |
So I managed to reproduce it. It's not really a minimal project but a template one from Unity.
|
@nakedpony - can you check if this happens only with 1.6 or also with 1.5 (for some it doesn't work in neither of them, dotnet/vscode-csharp#812 (comment)). Thanks! |
@jrieken Version 1.5.3 (1.5.3) works just fine. So I guess to me it would be a nice workaround so far. |
Given that this is tagged 'needs more info': I posted more info & another non-Unity sample project that exhibits the issue at dotnet/vscode-csharp#812 (comment) . |
@dbaeumer this is my console output |
Same problem here...
@dbaeumer The developer console contains an error: |
Exact same problem here. I downgraded to 1.5.3 and disabled auto-updates for now. That solved it. |
@vbrosch Your problem seems to be different and it's likely a comment in one of the JSON-files. |
Thanks for all the input. Closing this as a duplicate of dotnet/vscode-csharp#812 as I suspect OmniSharp diagnostics provider (dotnet/vscode-csharp#812 (comment)) |
@jrieken Sorry It took me so long to get back to you. Work has been crazy these last couple days. As indicated above, if I revert to 1.5.3 things work again. I tried your sample project, and I couldn't get it to do it again either. However, in my project that is happening in, I see two errors in the dev console:
So, yeah looks like an omni-code thing. I'll add info to their bug as well. Thanks! |
@dijitalmunky: Head over to dotnet/vscode-csharp#812. We've got a solution in progress there. |
After upgrading from 1.5.3, Intellisense and Error Detection seem to have stopped working. I am coding a .NET Core project written in C#.
What happens is that Intellisense and Error Detection show up (i.e. the red squiggly underlines) when I make an edit in my C# file. However, after a moment, they disappear again and I can't get them to stay visible.
I noticed that JS/Node/Typescript users seem to be having a similar issue, So I will mention that we do have one JS file in this project as well as a
package.json
. The purpose of this one JS file is to do a cross-platform script that will build the whole project in one go. Regardless, this issue happens no matter if the JS File is opened or closed in VS Code.The text was updated successfully, but these errors were encountered: