-
-
Notifications
You must be signed in to change notification settings - Fork 33
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 using the new LSP version of vscode-csharp? #853
Comments
@devlead has had some first-hand contact with the new version, so he might have some insights. As far as I know, there is no way to make this work, since in the new version Microsoft has dropped all support for external/non-ms/whatever integrations. |
😬 I see. Thanks for the quick feedback! |
There was some hint of "things to come" but that's in the future, for now. See https://twitter.com/timheuer/status/1710689194203394392?t=MXWzLaMZ9rOavCo3oXvHqQ&s=19 or, more directly, dotnet/roslyn#68696 |
🤞🏼 |
So currently all APIs in DevKit are for Microsoft internal use only, reached out to @timheuer and he pointed us to this as on of the issues for tracking progress in that area OmniSharp isn't on by default since they shipped C# DevKit, but you can turn it on. Try in your workspace adding settings "dotnet.preferCSharpExtension": true,
"dotnet.server.useOmnisharp": true Then reinstall cake intellisense and restart Code, then OmniSharp project selection should work. This way you can for one workspace/repo opt-in to OmniSharp, but use DevKit for all others as default. |
Is there any way of getting IntelliSense working using the new LSP version of vscode-csharp (>= v2.0) where OmniSharp is no longer used? Or would one have to re-enable OmniSharp for that to work?
The text was updated successfully, but these errors were encountered: