-
Notifications
You must be signed in to change notification settings - Fork 677
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 fails to run with the new 1.19 update #2992
Comments
I have also been running into issues and have to force the version back to 1.18 every time I start VSCode (because the add-on keeps trying to auto update) Environment Information.NET Core SDK (reflecting any global.json): Runtime Environment: Host (useful for support): .NET Core SDKs installed: .NET Core runtimes installed: VSCode Version: 1.33.1 |
@rtablada, as a temporary workaround, before installing specific version 1.18 you can disable autoupdating here: |
Latest OmniSharp requires .NET 4.7.2, see https://github.com/OmniSharp/omnisharp-roslyn/blob/master/CHANGELOG.md#13214---2019-04-08 |
@filipw ugh, annoying at the very least. i assume this was done because some feature specific to 4.7.2 was required, rather than just updating for the sake of it. the portion of the userbase that refuses to update because the release build of windows 10 has a friendly way of disabling automatic updates, is dropped once again. |
@filipw Is a specific minor version of .NET 4.7.2 needed? I have .NET 4.7.2 installed (even target it for a few applications) and yet I'm facing this same problem, as reported on #2997 |
Yes, unfortunately MSBuild 16, which was introduced in this latest build of OmniSharp as part of .NET Core 3.0 support requires .NET 4.7.2 to run. Note that there is a new build to try out, that will at least prompt you to install .NET 4.7.2 instead of failing silently #3004 (comment) Sorry for your troubles - at this point there is no way we can support both new .NET Core 3.0 stuff and old OS builds (Windows 10 1507 reach end of life 2 years ago I believe). |
Very sad situation where Windows 7 is supported but the release version of Windows 10 isn't. 👍 for the update though. |
Why .Net Framework?? |
@bruce31 OmniSharp does NOT run on .NET Framework on macOS/Linux. On macOS/Linux, it will run on Mono. On Windows it will run on the full .NET Framework. |
It is ironic that in order to support .Net Core 3.0 it forces an upgrade of Full Framework when the selling point of 3.0 is that windows desktop apps can use the latest and greatest, independent of the version of full framework installed on the system. |
Issue Description
OmniSharp fails to run with the new 1.19 update.
Note I am running an older version of Windows 10 that does not support .NET Framework 4.7:
Steps to Reproduce
Expected Behavior
OmniSharp works and detects problems.
Actual Behavior
OmniSharp crashes on startup.
Logs
OmniSharp log
OmniSharp server started.
Path: C:\Users\mat1jaczyyy.vscode\extensions\ms-vscode.csharp-1.19.0.omnisharp\1.32.18\OmniSharp.exe
PID: 764
System.IO.FileNotFoundException: Could not load file or assembly 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified.
b__1()File name: 'netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
at OmniSharp.Stdio.Driver.Program.<>c__DisplayClass0_1.
at OmniSharp.HostHelpers.Start(Func`1 action)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
[ERROR] Error: OmniSharp server load timed out. Use the 'omnisharp.projectLoadTimeout' setting to override the default delay (one minute).
C# log
Environment information
VSCode version: 1.33.1
C# Extension: 1.19.0
Dotnet Information
.NET Core SDK (reflecting any global.json): Version: 2.2.105 Commit: 7cecb35b92Runtime Environment:
OS Name: Windows
OS Version: 10.0.10240
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.2.105\
Host (useful for support):
Version: 2.2.3
Commit: 6b8ad509b6
.NET Core SDKs installed:
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.302 [C:\Program Files\dotnet\sdk]
2.1.502 [C:\Program Files\dotnet\sdk]
2.2.105 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.3 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download
Visual Studio Code Extensions
The text was updated successfully, but these errors were encountered: