Spencer G. Jones
Spencer G. Jones
I see the blocking issue from last time is still open: https://github.com/OmniSharp/omnisharp-roslyn/issues/2259
I am seeing this error too. I am guess it is the same issue as [this](https://github.com/dotnet/aspnetcore/issues/28112), but the fix there doesn't appear to be applicable to .NET Framework.
This appears to be caused by the upgrade to ASP.NET Core 2.2.0. Downgrading back to 2.1.1 like I have done in [this branch in my fork](https://github.com/mispencer/omnisharp-roslyn/tree/DowngradeTo211) appears to solve this...
This continues to be a blocking issue for our use case.
I created [a fork of Omnisharp](https://github.com/mispencer/omnisharp-roslyn/tree/DowngradeTo211) that supports .NET 6 earlier that I personally use, but it is a ugly hack. However, it doesn't appear that the Omnisharp maintainers will...
I created a PR on the Omnisharp repo to resolve the blocking issue: https://github.com/OmniSharp/omnisharp-roslyn/pull/2446
It works in my testing. Are you using the new executable in ymcd? Steps to using this Omnisharp fork: 1. Clone [my fork](https://github.com/OmniSharp/omnisharp-roslyn/pull/2446) somewhere 2. Build it: `dotnet build .\src\OmniSharp.Http.Driver\OmniSharp.Http.Driver.csproj`...
That is correct. There is a stable release now.
We have seen this error many times in our CI docker builds as well. It appears to occur when the hosting VM is low on system resources.
I intended to wait until this PR has been reviewed, but ok. I have created related PRs in the documentation and spec projects.