neotest VS omnisharp-vscode

My first neovim plugin project was to write an adapter (runner) for neotest, for a language that I use regularly and which was missing from the existing adapters.

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Here's some things that may help: - https://github.com/mfussenegger/nvim-dap + dap ui - https://github.com/nvim-neotest/neotest

I use neotest to run tests (with pytest).

For testing I use https://github.com/nvim-neotest/neotest which gives a nice outline.

For those who don't know it, it's an adapter for neotest, a Neovim plugin that

You might look at how Neotest handles this, or even see if you can use/contribute to that project directly. It already has support for a fair number of languages at varying levels of maturity.

I am writing Python these days, and LSP + DAP + neotest give me 90% of what PyCharm would have given me. I don't know how well this works with Java, the latter two did not exist when I was still writing Java. The way I did it was use Neovim with jdt-ls to write code and IntelliJ for debugging. Debugging does not require switching between keyboard and mouse, so it was OK to me.

I'm sure that we could figure out a way to install rocks without luarocks, but it's still going to be an additional step with possible complications. Personally, I would rather just embed the library within my plugin like neotest does with xml2lua. The marginal cost of a slightly larger install is more than paid for by an easier install process and a guarantee that it works.

They announced a year ago they are working on better C# support in VSCode https://github.com/omnisharp/omnisharp-vscode/issues/5276

OmniSharp (soporte de C# en VS Code): Licencia MIT

Let me try to find that post. It's basically the drama around this

> They did a wonderful job with C# and .NET Core.

And VSCode. One thing all three have in common is that they are all FREE to use--they don't make Microsoft any money directly.

And, for the segment of the developer tools market that wrangles C# code, if VSCode gets too good, it becomes a threat to a cash cow: Visual Studio.

Start here: https://github.com/OmniSharp/omnisharp-vscode/issues/5276#is...

Sounds like this issue https://github.com/OmniSharp/omnisharp-vscode/issues/2513

Open source. OP is referencing a decision Microsoft made last year to include some closed-source components, in particular the debugger from Visual Studio, in the default C# extension for Visual Studio Code. There is a Samsung-provided open source debugger available if you absolutely require it, but the closed source stuff doesn't have any usage restrictions afaik.