-
Notifications
You must be signed in to change notification settings - Fork 689
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 no longer working for Web API project #2997
Comments
Can confirm this is an issue.
Output of "Log (Extension Host)":
|
in this case the error comes from an external extension, |
Seems like the error was due to the latest version of the C# extension. When installing latest version (1.19.0), the above error occurs. |
I'm seeing this too on MacOS Mojave, VSCode 1.33.1, and omnisharp-vscode 1.19. |
Same behavior here - Windows 10, VS Code 1.33.1, and omnisharp-vscode 1.19. Omnisharp Log stops at adding project, but on extension host, these logs keep appearing:
Weirdly enough, this happens on a specific project but not on another. I've tried to make the one working break as the other one and fix the broken one based on the working one but I've failed on both attempts. Only rolling back to 1.18 makes the intellisense work again on the broken project (but VS Code keeps updating it back, so this workaround is quite a pain) The same thing happened to another developer on another machine on the same broken project. Rolling back to 1.18 also solved the problem (so it seems to be a specific kind of project on the 1.19 version of the omnisharp-vscode that is consistently breaking). Unfortunately neither of the projects I have are open source. |
@dietermijle, does your .csproj file have any stars (*) for package versions? This problem might be the same as #3009 . The project that I 've mentioned that has broken intellisense on 1.19 apparently works fine now after changing the stars to '0' and restarting VS Code. The project that was working fine all along didn't have any stars on the .csproj. |
My sln definitely has a lot of wildcards in the csproj files.
… On Apr 18, 2019, at 10:00 AM, Thomaz Moura ***@***.***> wrote:
@dietermijle, does your .csproj file have any stars (*) for package versions? This problem might be the same as #3009 .
The project that I 've mentioned that has broken intellisense on 1.19 apparently works fine now after changing the stars to '0' and restarting VS Code. The project that was working fine all along didn't have any stars on the .csproj.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@achandlerwhite can you remove the wildcards and restart VS Code to check if this is indeed the same issue? |
I will give it a try this evening.
Update: my solution has 17 projects in it--I tried removing wildcards from one to see if it mattered, but no luck. Looks like they already merged in a fix in Omnisharp-roslyn.
… On Apr 18, 2019, at 10:19 AM, Thomaz Moura ***@***.***> wrote:
@achandlerwhite can you remove the wildcards and restart VS Code to check if this is indeed the same issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
This behavior was caused by wildcards in package/framework references that unfortunately caused OmniSharp to get stuck in an initialization infinite loop. I will close this is a duplicate of #3009 Thanks everyone for helping on this. |
Im currently having the same problem tho i dont have any wildcard in my .csproj or packages.config. UpdateI've tried to use the Beta version provided in #3009 which resulted in the same error
|
I can confirm this bug already exists.
|
This bug still exists. Is there any update fixing it coming? |
Getting the following error recently when loading my solution in VS Code.
OmniSharp log stops at 'Adding project' for first project in the solution
As a result, my Intellisense is no longer working.
Any idea how to resolve this?
I tried uninstalling & re-installing VS code completely, but without success.
The text was updated successfully, but these errors were encountered: