Ready to run is enabled for better startup times. OmniSharp still ships STDIO and HTTP variants, and both have been upgraded to. NET/.NET Core versions as well, as long as you have the necessary SDK installed, it's just for its own startup it requires you to have. Since SDK is needed for MSBuild, we take advantage of it to run OmniSharp as well, because it solves certain distribution problems that arise when using self-contained applications, most notably, code signing is required for self-contained MacOS applications. The reason is with this variant OmniSharp no longer bundles its own MSBuild but instead uses one from the SDK. NET 6.0 SDK to be installed on your machine. NET 6.0 is published as framework dependent application, not a standalone application, meaning it requires. I myself worked on developing this from my M1 Mac, dogfooding OmniSharp and it has been a real joy seeing that work. This of course means that we now have native builds for ARM as well, which is very cool. It gets published for the following RIDs: NET 6.0 build of OmniSharp published as build artifact. NET 6.0 build is much faster and a lot more stable, and is the first step towards retiring the. This is a big milestone in the OmniSharp project as the. NET 5-based variant of OmniSharp, though that one was never released.
The related feature branch was maintained for over a year, and previously contained a. On Decemwe released version 1.38.0 of OmniSharp which, for the first time, included.
0 kommentar(er)
