Omnisharp fails on OSX
See original GitHub issueIssue Description
Omnisharp fails with
OmniSharp requires a complete install of Mono (including MSBuild) to provide language services when omnisharp.useModernNet
is disabled in Settings. Please install the latest Mono and restart.
omnisharp.useModernNet
is disabled in settings already.
Steps to Reproduce
Just open project
Expected Behavior
Omnisharp should work
Actual Behavior
Omnisharp fails with
OmniSharp requires a complete install of Mono (including MSBuild) to provide language services when omnisharp.useModernNet
is disabled in Settings. Please install the latest Mono and restart.
Logs
OmniSharp log
OmniSharp failed to start because of missing requirements. OmniSharp failed to start because of missing requirements. OmniSharp failed to start because of missing requirements. OmniSharp failed to start because of missing requirements.
C# log
empty
Environment information
VSCode version: 1.73.0 C# Extension: 1.25.1
Mono Information
OmniSharp using mono: 6.12.0Dotnet Information
.NET SDK (reflecting any global.json): Version: 6.0.401 Commit: 0906eae6f8Runtime Environment: OS Name: Mac OS X OS Version: 13.0 OS Platform: Darwin RID: osx-arm64 Base Path: /usr/local/share/dotnet/sdk/6.0.401/
global.json file: Not found
Host: Version: 6.0.9 Architecture: arm64 Commit: 163a63591c
.NET SDKs installed: 6.0.401 [/usr/local/share/dotnet/sdk]
.NET runtimes installed: Microsoft.AspNetCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.9 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Download .NET: https://aka.ms/dotnet-download
Learn about .NET Runtimes and SDKs: https://aka.ms/dotnet/runtimes-sdk-info
Visual Studio Code Extensions
Extension | Author | Version |
---|---|---|
better-cpp-syntax | jeff-hykin | 1.16.3 |
cpptools-themes | ms-vscode | 2.0.0 |
csharp | ms-dotnettools | 1.25.1 |
csharpier-vscode | csharpier | 1.3.5 |
debugger-for-chrome | msjsdiag | 4.13.0 |
isort | ms-python | 2022.4.0 |
jupyter | ms-toolsai | 2022.9.1202862440 |
jupyter-keymap | ms-toolsai | 1.0.0 |
jupyter-renderers | ms-toolsai | 1.0.12 |
python | ms-python | 2022.18.1 |
remote-containers | ms-vscode-remote | 0.262.3 |
remote-ssh | ms-vscode-remote | 0.90.1 |
remote-ssh-edit | ms-vscode-remote | 0.84.0 |
remote-wsl | ms-vscode-remote | 0.72.0 |
textproto-grammer | thejustinwalsh | 0.0.8 |
vetur | octref | 0.36.1 |
vim | vscodevim | 1.24.3 |
vscode-bazel | BazelBuild | 0.6.0 |
vscode-docker | ms-azuretools | 1.22.2 |
vscode-jupyter-cell-tags | ms-toolsai | 0.1.6 |
vscode-jupyter-slideshow | ms-toolsai | 0.1.5 |
vscode-proto3 | zxh404 | 0.5.5 |
vscode-pylance | ms-python | 2022.11.10 |
vscode-remote-extensionpack | ms-vscode-remote | 0.21.0 |
vscode-solution-explorer | fernandoescolar | 0.7.4 |
vscode-typescript-tslint-plugin | ms-vscode | 1.3.4 |
Issue Analytics
- State:
- Created 10 months ago
- Reactions:4
- Comments:7 (2 by maintainers)
Downgraded to 1.25.0
I’ve never had to downgrade a VSCode extension, so for anyone else who doesn’t know (cc @rohitvishwakarma1819) :
And select 1.25.0
The same problem occurs in Linux Ubuntu 20.04