Fred Silberberg
Fred Silberberg
@stephentoub is there anything blocking this suggestion? Can we tag it for review?
@JosefPihrt you will need to update this analyzer for .NET 6: with the interpolated string changes and `DefaultInterpolatedStringHandler`, no boxing is incurred here.
Looks like this was broken by https://github.com/dotnet/roslyn/pull/60266. @JoeRobich, can we move that provider back down to the Features layer?
@JoeRobich @filipw for review.
We'd need to see the log from the omnisharp server. But at a guess, something is messed up with your configuration.
From the log, it doesn't look like O# was able to find your dotnet installation, which will be why it can't find the reference assemblies. How did you install dotnet?
I'm not particularly familiar with OSX troubleshooting, maybe @filipw has an idea on how fix it?
I don't think it's similar at all, as osx applications generally install in a very different way than Linux applications. I wouldn't expect to see this issue on Linux, as...
[Omnisharp does not require mono to run](https://github.com/OmniSharp/omnisharp-vscode/issues/5120). What it should be doing is finding the location of the dotnet msbuild (not the mono msbuild) and using the reference assemblies from...
The emacs startup scripts you're using not using the modern version of OmniSharp does not mean that OmniSharp requires mono to run. It just means that the emacs scripts you're...