while i was gone for summer the c# extension for #vscode updated to play nice with #microsoft's new c# dev-kit -extension.

apparently that defaults to no longer using #omnisharp as the engine.

the new engine, spiffy as it may be, does NOT play nice with coge-generators and gave me lots of errors in intellisense.

so: #tipOfTheDay for #csharp #developers using vscode: switch the extension back to using omnisharp (it's a setting), and reload.

happy days again!

When using #Eglot how does it decide which files it will search for xref-find-definitions? Does that depend on the language server? Trying to use #omnisharp but can't get it to see anything outside of the file I'm currently editing. Any ideas?

#Emacs

Trying to set up dotnet development in neovim and having problems.
I get code completion and errors/warnings working but things like code actions or go to definition does not work.
Anyone who has gotten this working and wouldn't mind lending a hand?
#softwaredevelopment #dotnetcore #dotnet #vim #lsp #omnisharp #neovim

This is first time I am enjoying #VSCode with #omnisharp! I installed Mono, and added it to omnisharp and now I can statically analyze a .NET Full framework app on a Mac! And fix errors. :)

somehow it seems that openssl3 broke omnisharp, and I'm not really sure how that's possible. It ate my whole morning.

I'm hoping the .NET 7 launch tomorrow will bring an update that makes it moot, so I don't have to deal with it, but we'll see.

#dotnet #neovim #omnisharp #arch #archbtw #wsl