try-convert VS omnisharp-vim

dotnet upgrade assistant or dotnet try-convert can help with that.

- dotnet try-convert: https://github.com/dotnet/try-convert

try-convert

Check out https://github.com/dotnet/try-convert

https://github.com/dotnet/try-convert (usually) makes this a breeze.

I'm looking to move one of our software suites from .NET Framework 4.7 to .NET 6. A lot of online guides recommend starting with the Microsoft conversion tools to ease/speed up the process. There seem to be two tools that are used for it try-convert and upgrade-assistant. However, I'm not sure I understand the difference between them and when should I use which tool (assuming that it matters).

That would mean you have pretty simple code then, relatively speaking. I helped write the underlying project conversion tool used in the Migration Assistant and found that there's a lot of big and incompatible differences well before you even get into which APIs you're using. Lots of enterprise apps end up using them, whether or not the authors of those apps are aware of it.

migrate to SDK-style project files - try-convert does wonders here

Are you using .NET SDK-style projects, or the old scary ones? The latter should load, but since you can't even create them anymore I would expect them to bit rot over time. The try-convert tool should be able to help with that (I wrote most of it, plus the F# support!)

there's https://github.com/dotnet/try-convert. Haven't tried it; I instead use https://github.com/hvanbakel/CsprojToVs2017, but I assume the former might be a better choice by now.

You can probably use omnisharp-vim (OmniSharp is the same tech that powers VS Code's C# experience).

https://github.com/OmniSharp/omnisharp-vim

https://github.com/OmniSharp/Omnisharp-vim is a thing, but I don’t know how good it is. I would probably go with VSCode or Rider (and their respective Vim plugins), as they are quite productive for .NET.

With respect to C#, have you looked at the [OmniSharp](https://github.com/OmniSharp/Omnisharp-vim) plugin?

Then use this if you don't want to use VS Code.

There's a language server for vim (and neovim): https://github.com/OmniSharp/Omnisharp-vim

Are you using omnisharp-vim? It works well in my neovim setup and configuring it was pretty straightforward!

I'm not sure if you are using the omnisharp command as an example or something you'd like to be able to do, but if it's the latter check out omnisharp-vim! I use it as my LSP for C# development and it integrates most all of omnisharp's functionality with neovim very well.

So OmnySharp has a help document „integrated“. Just type :h omnisharp-vim into vim and you should see it. Alternatively you can go to https://github.com/OmniSharp/omnisharp-vim/blob/master/doc/omnisharp-vim.txt and look at it there. In general: if a plug-in provides documentation, it’s probably stored under /doc/.txt As the c# langauage server is not a vim plug-in, it does not follow this standard. So I unfortunately can’t help with that.