-
Notifications
You must be signed in to change notification settings - Fork 685
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
Omnisharp doesn't work, VSCode output doesn't even include Omnisharp in the dropdown list #1867
Comments
Same for me. It was working on 1.17 a couple hours ago then VSCode automatically updated to 1.18 and restarted and now Omnisharp doesn't work anymore. Nothing else changed.
Tried the same steps to fixing it as @shalevy2888 |
Could you check your |
Only one extension installed, here is the ls: |
Same here.
After updating to 2.0.2 using this omnisharp works again. |
Only got one extension installed. After installing .Net SDK 2.0.2 as @ysris suggested I don't get the "failed to spawn dotnet" error anymore but Omnisharp is still not working |
@Sebioff don't know if it can help you but now
Is there anything interesting in the omnisharp log (vscode output, dropdown > omnisharplog) ? |
I have .NET 2.0.2 installed. |
FWIW, I have .NET Core SDK 2.0.2 installed as well. Yes, it seems like the VS Code extension failed to activate. Could you try invoking the |
The |
Restarting OmniSharp doesn't do anything. Also "OmniSharp: Select Project" shows 0 projects. |
|
I'm getting this Error on the Developer Tools Console: Not sure if it's related. |
Restart Omnisharp doesn't work for me too on 1.18, output and developer tools console are empty. |
Same thing. Stop working on 1.18 |
Note that the version of VS Code (1.18) is orthogonal to the version of C# for VS Code that you have installed (the latest is 1.13.1) |
Yes, C# for VS Code version 1.13.1 is installed. Any further logs to check or things to try? I'll gladly provide and test anything that might help resolve this. |
Same problem. Stop working on 1.18 and no omnisharp log ouput dotnet --info
.NET Command Line Tools (2.0.2)
Product Information:
Version: 2.0.2
Commit SHA-1 hash: a04b4bf512
Runtime Environment:
OS Name: Mac OS X
OS Version: 10.12
OS Platform: Darwin
RID: osx.10.12-x64
Base Path: /usr/local/share/dotnet/sdk/2.0.2/
Microsoft .NET Core Shared Framework Host
Version : 2.0.0
Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d I try it with the insider preview of vscode (1.19) and all working fine. |
Does Omnisharp has any logs it produces that I can look at? If yes, where are they located in Mac? |
|
Sorry for the confusion. Right now Omnisharp doesn't even start (I suspect) so there is no log inside of VSCode. Omnisharp isn't part of the dropbox. From the thread I understand others are experiencing the same. My question was of other logs, in some local folder on my drive that I can look at... |
I would be interested to know if there is even a |
Yes, both folders exist and contain a whole bunch of dlls and the Omnisharp/debugger exes |
Yes, they exist. If I remove the extension and reload vscode and than install and reload, both OmniSharp and .Net are downloaded and installed. But other than that I don't see any logs... |
@shalevy2888 : You're on OSX, right? Could you try running the following command in a Terminal window?
Let me know the output. |
Here is what I get when running the above command (sorry for the long log). I do see this message inside: Omnisharp server running using Stdio at location.
|
Great! It looks like the problem isn't with OmniSharp itself and it loads your Unity projects correctly. Instead, it seems that the C# extension isn't triggering on your machine for some reason. @jrieken, do you know of any issues in VS Code 1.18 above extension loading? |
Got it to work!!!
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 |
Yes! Awesome :) |
@DustinCampbell
|
I found a solution to my problem, in "user settings" ->"files.exclude", i set "/.prefab" and "**.bin" to false instead of true before, it works again! I don't konw why but if you have the same problem you can check if you have the same settings as mine. |
FWIW, I believe this is a VS Code issue around extensions that activate on wildcards (such as *.csproj or *.sln) that was introduced in VS Code 1.18. It seems that something has changed in VS Code 1.19-insiders to address the problem. |
@DustinCampbell I tried 1.19-insiders, same error as 1.18, all these two version works after i set "/.prefab" and "**.bin" to false. |
I have the same problem on Windows with VS Code 1.19.2 / 1.20.0-insider and ms-vscode.csharp 1.13.1. Completions are missing. Here's my dotnet info:
Here's what I see in Log (Extension Host):
I don't see any problems if I run OmniSharp directly:
If that's a VS Code bug, where is it tracked? |
In case anyone else is wondering, my problem was solved by making OneDrive eagerly download files (even though OneDrive itself reported that the folder was downloaded completely). I will open a separate issue for that. |
Thanks @grofie! |
If you are using Unity and also have this problem too, please try out the fix I explained here and give me feedback if it is working for you too: dotBunny/VSCode#165 (comment) (Sorry, my first attempt was not fully matured, but hopefully it is working now) |
Got this issue... Im using latest VSCode (1.30.1) with corresponding Omnisharp (and Unity). After researching for a while, first removed the *.sln and .csproj files from VSCode excluded files, but wasnt enough. After some extra research, found this thread and got it working by removing the *.prefabs file extension from the exclusion list too (WTF?!? -excuse my french-, have no idea how that file type can break things down like that. How come more than a year later and after so many versions we can end on such a critical issue again? Thanks @Sebioff and anyone on this thread for the help. |
@rchande I meant extension as in file extension, not as in plugin. Sorry for the poor wording. Prefabs are file types used in Unity3D engine, for content, not configuration. There should be no reason whatsoever why adding that file extension to the exclusion list should break onmisharp loading. Thanks for checking. |
Fresh install at latest version of Visual Studio Code and this doesn't work. Same version on Elementary OS5 works just fine. |
Hi ! I and my coworkers ive been searching for days and tryed everything but didnt worked, but we found a solution i dont really know if it will work for everyone . |
Guys, I did this and it started working. I closed the VS Code Studio. then start debugging |
Hello everyone, now I'm in trouble with this error, after searching a bunch of resources but still stuck on this! I tried the solutions you guys mentioned above, but none of them worked! |
@TKNguyen12a9 Can you please open a new issue and provide the information requested in the template? It would be helpful to know what type of project your are trying to open (Web, Unity, Console, etc...), does your code have a project file (.csproj) or solution (.sln), whether it can be built from the commandline with |
This is still a problem. I'm running Garuda Linux. VS Code and C# extension are up-to-date, This is a project that is freshly-built using The Language Server starts but there is no sign of Omnisharp anywhere in VS Code except a few configuration options. There are no command palette entries, there is no log selection in the Output palette, and autocompletion does not work. I've tried manually setting the Omnisharp path to the output of |
A lot has changed with packaging and acquisition of necessary components since this issue was opened. If this is still an issue, please open a new issue with details. |
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:
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
The text was updated successfully, but these errors were encountered: