OmniSharp/omnisharp-emacs

Migration to omnisharp-roslyn

razzmatazz opened this issue · 2 comments

razzmatazz commented

This is a placeholder issue for providing information and tracking problems related to rollout of omnisharp-emacs roslyn branch to master and the subsequent melpa release. Users of the package will be directed here by omnisharp-emacs once it detects there has been an upgrade from the old version. See #276

Why we broke your setup

Omnisharp-server has been rewritten and is currently reincarnated as Omnisharp-roslyn.

The new server has new features as it reuses the Microsoft Roslyn framework and allows for a stdio communication with the editors/clients which makes management and integration somewhat better with emacs. (HTTP transport is still available with the new version of omnisharp-emacs.)

Omnisharp-emacs has been updated to use the new server and we didn't want to maintain compatibility with the old server thus this is a breaking release for some of the users.

Also note that some of the features from the old version are not yet implemented, any help is appreciated.

Upgrade instructions

Mostly, you need to:

Please register an issue or comment on this one if anything does not work for you.

Alternative to upgrade (downgrade)

You may want to keep the old omnisharp-emacs installed, in case you don't want to update or it doesn't work for you for some reason (we want to know though! – please register github issues on this).

Your options for installing the old omnisharp-emacs are:

Comments?

Feel free to register new issues or just write a comment on this issue w.r.t. your upgrade experience/problems/etc.

razzmatazz commented

This happens often (after upgrades?) on the new/roslyn version, didn't find the reason yet:

  • #308 (function definition is void : omnisharp--path-to-server)
razzmatazz commented

Closing this issue as it is mostly for documentation anyway.