question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Omnisharp stopped working with a Failed to spawn 'dotnet --info' log

See original GitHub issue

Environment data

dotnet --info output: “Failed to spawn ‘dotnet --info’” VS Code version: 1.8.1 C# Extension version: 1.6.2

Steps to reproduce

Starting vs code and change language to c#

Expected behavior

Omnisharp starting up and working

Actual behavior

Omnisharp simply disappeared.

As stated above, I started coding for unity with Omnisharp and vscode last week and everything is fine. However, after the new year break, when I returned this week, Omnisharp just stopped working for no reason. the little fire icon disappears, both c# and omnisharp log is empty, intellisense gone.

I tried to uninstall and reinstall the C# extension from vs code and when the extension tries to download and install omnisharp, it ended up with a “Failed to spawn ‘dotnet --info’” log after downloaded both omnisharp and the .NET Core Debugger. Uninstall vscode and deleting everything under both the extension folder and the appdata folder doesn’t help either. All I got now is an error message in C# log every time I start up vs code and it’s always this “Failed to spawn ‘dotnet --info’”

What should I do to locate the cause of the problem and bring back Omnisharp??

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:13 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
DustinCampbellcommented, Jan 4, 2017

The best answer I can provide is to fully remove the C# extension and reinstall it. However, the problem that you’re describing does not sound like it is related to the C# extension. I have a hard time believing that nothing has changed on your machine. 😄

To uninstall, try the following:

  1. Close Visual Studio Code.
  2. Browse to %UserProfile%\.vscode\extensions and delete all ms-vscode.csharp-* extensions.

Now, open Visual Studio Code and reinstall from the Extensions pane.

2reactions
Fire1nRaincommented, Jan 4, 2017

OMFG!!! I’m such a dumb-ass!! The .sln and project.json files under my project somehow disappeared and I didn’t noticed it!! Sorry for all the trouble @DustinCampbell @gregg-miskelly , I feel so dumb after finding out the cause. Also, Can you guys add a notification or something like “No .sln file found!” for dumb people like me?

Read more comments on GitHub >

github_iconTop Results From Across the Web

c# - .NET Core, failed to spawn dotnet --info
I ran in to this myself. You may have missed the bit of info in the header that pointed you to this URL....
Read more >
Visual Studio Code extension OmniSharp does not detect . ...
Problem is, the OmniSharp extension in Visual Studio Code doesn't seem to detect it. "Failed to spawn 'dotnet --info'" shows up in the ......
Read more >
Visual Studio Code - ArchWiki
Code is a cross-platform text editor developed by Microsoft, built on the Electron framework. Visual Studio Code is a binary distribution of ...
Read more >
Visual Studio Code Intellisense
I believe my problem lies with omnisharp, as whenever I try to ... it says 'failed to spawn dotnet --info', and I think...
Read more >
Microsoft C# Extension for VSCode cannot find .NET Core SDK
Issue Description · Steps to Reproduce · Expected Behavior · Actual Behavior · Logs · Environment information · Mono Information · Dotnet Information....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found