Aspnetcore: Update Omnisharp to Roslyn 3.7

Created on 20 May 2020  路  7Comments  路  Source: dotnet/aspnetcore

We can't update to Roslyn 3.7 until Omnisharp does because types passed between our projects need to be recognized as of the same type.

@JoeRobich is there an ETA on OmniSharp taking 3.7?

CC @NTaylorMullen

Done External Resolved area-razor.tooling feature-razor.vscode

Most helpful comment

@ryanbrandenburg I'll look into getting it updated to a recent build tomorrow morning.

All 7 comments

@ryanbrandenburg I'll look into getting it updated to a recent build tomorrow morning.

fyi @captainsafia

Thanks @JoeRobich! Let us know how this goes today.

Synced with @JoeRobich out-of-GitHub. It looks like the Roslyn update will happen so we do not need to worry about reverting on our end.

@captainsafia I updated OmniSharp to Roslyn 3.7. Will do a new release of OmniSharp once this goes in https://github.com/OmniSharp/omnisharp-roslyn/pull/1805. Then I can update the C# extension.

New release of OmniSharp is live with Roslyn 3.7.0. https://github.com/OmniSharp/omnisharp-vscode/pull/3799 is the PR to update in the C# extension.

And we now have a new C# prerelease using the new OmniSharp. Once the razor tooling it updated, we can get a build out to vendors for prerelease testing.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

markrendle picture markrendle  路  3Comments

ermithun picture ermithun  路  3Comments

UweKeim picture UweKeim  路  3Comments

farhadibehnam picture farhadibehnam  路  3Comments

fayezmm picture fayezmm  路  3Comments