Is this project still alive???

[brad-jones]

Hasn't been any releases since August. Will omnisharp-atom ever work with .net core 1.1 and future versions? Or has it been abandoned in favor of Visual Studio Code?

[ignism]

I'm a bit sad this is still floating around here unanswered.

[david-driscoll]

@ignism @brad-jones sorry guys, I've been busy with plenty of other work (and real life 😢).

I'm trying to make sure things keep working, and sometimes it's a little slower than I'd like, so I'm sorry about that! I'm going to see if I can come triage some of these issues this weekend.

Also going forward, atom is going to support LSP so that may be the path we take forward to let OmniSharp work everywhere.

[ignism]

I see there are some LSP packages. When I try to install it manually, it cant find the atom-languageclient module. However, I did install that package. Any thoughts? I am a bit fed up with the errors Omnisharp gives me every now and then and would love to help test that new LSP thingy.

[willl]

Hi @ignism, this is the atom-languageclient repo.

And as they say on that page, C# support is experimental. I know @damieng was one of those behind that effort.

As @david-driscoll has mentioned, he's working on adding LSP support to omnisharp-roslyn.

Unfortunately there isn't any developers (other than @david-driscoll, who is working on a ton of other things at the same time) actively working on omnisharp-atom at this point in time. However, help is welcome if anyone wishes to (and is able to) contribute.

I think the eventual plan would be to have atom-languageclient talking to languageserver-csharp which will then talk to the omnisharp-roslyn server. Right now, languageserver-csharp talks to omnisharp-node-client which then talks to omnisharp-roslyn. So lots of layers involved.

Not ideal I know. But that's the state of things from what I can see.

[damieng]

Hey @ignism as atom-languageclient and languageserver-csharp aren't published yet - they're quite experimental - you'll need to check out the source for atom-languageclient then npm link the folder so that languageserver-csharp works.

You'll also need to install Nuclide for now to get the UI side of things (error messages, outline view, go to definition etc)

If you have any more questions feel free to raise an issue on either of those repos. The long-term plan is for languageserver-csharp to bind to whatever the best LSP-capable version of Omnisharp is :)