vscode-csharp: Omnisharp doesn't work, VSCode output doesn't even include Omnisharp in the dropdown list

Environment data

dotnet --info output: Product Information: Version: 2.0.2 Commit SHA-1 hash: a04b4bf512

Runtime Environment: OS Name: Mac OS X OS Version: 10.13 OS Platform: Darwin RID: osx.10.12-x64 VS Code version: 1.18 C# Extension version: 1.13.1

Steps to reproduce

After automatically getting the latest VSCode (1.18 with blue icon now) and re-installing the C# extension, Omnisharp doesn’t work.

Tried:

opening many different projects
Removing and installing the extension
removing and installing VSCODE
Installing Mono and dotnet again and again 😃
Installing Omnisharp with Brew

What I really would like is to have some hints on how to debug why it doesn’t work on my system. I assume this is a user issue, but I already spend 3 hours trying to debug without any success. I tried also to enable: “omnisharp.loggingLevel”: “debug” - but since the output doesn’t include Omnisharp it doesn’t really help…

Any help?

Thanks!

Expected behavior

Actual behavior

About this issue

Original URL
State: open
Created 7 years ago
Reactions: 4
Comments: 46 (12 by maintainers)

Most upvoted comments

Yes! Awesome 😃 Didn’t even need to uninstall/reinstall Omnisharp, just had to find and remove the problematic exclude. In my case it was "**/**.prefab": true,

Sebioff on Nov 21, 2017

Thanks @grofie!

DustinCampbell on May 29, 2018

Got it to work!!!

I got a weird error while doing global find in VSCODE, something about error parsing glob. Found a solution online: https://github.com/Microsoft/vscode/issues/25923 which indicate I might be excluding more file types than I should.
I removed the *.sln exclude from my settings and it solved the global find problem. I then thought it might be related…
I uninstalled c# extension, reloaded VSCODE. Installed again, reloaded, let the extension download and install Omnisharp - and it works!

This exclude isn’t new in my settings and it was working without a problem in the previous version of VSCODE. So I’m guessing they changed something and it caused the extension to fail as well.

I would have thought the exclude feature of VSCODE is cosmetic only, just what to show or not show in the file browser, but it has too much hidden functionality. I guess I’m going to remove all the excludes.

Thanks all for trying to help. I wonder if this fixes the issue for the other people in this thread.

Shay

shalevy2888 on Nov 19, 2017