persp-projectile VS omnisharp-vscode

I am currently trying with perspective rather than persp-mode, as it segregates the buffer list as I like (#1 above). I've got projectile with persp-projectile, and that seems to give me what I need for project navigation (#2 probably, still not 100%). I get some help in my mode line for project focus (#3, partially).

Aye. I often have two interdependent projects I work on simultaneously, and I use a lot of persp-projectile (https://github.com/bbatsov/persp-projectile). I would love to try project.el but sadly it seems like it doesn't integrate with perspective.el yet.

I also use purely emacs for "commercial programming" (as you refer to it) and for managing multiple projects I use projectile + perspective + persp-projectile.

I had my own rolled version of this in my config until recently when I swapped to perspective and perspective-projectile.

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.