OmniSharp-Roslyn is a .NET development platform based on Roslyn workspaces. It provides project dependencies and language syntax to various IDE and plugins.

OmniSharp-Roslyn is built with the .NET Core SDK on Windows and Mono on OSX/Linux. It targets the net46 target framework. OmniSharp requires mono (>=5.2.0) if it is run on a platform other than Windows.

In addition, if you need the HTTP interface and you want to run on Linux, you'll also need to make sure that you have libuv installed.

See our change log for all of the updates.

Pre-release versions are available in azure storage, they can be viewed here.

All changes to master will be pushed to this feed and will be made available with the following convention: https://roslynomnisharp.blob.core.windows.net/releases/{version}/{packagename}-{os/arch}.{ext}

• Version is auto incremented and is visible in the travis or appveyor build output
• Package Name would be either omnisharp or omnisharp.http
• os/arch will be one of the following:
  • win-x64
  • win-x86
  • linux-x64
  • linux-x86
  • osx
  • mono (Requires global mono installed)
• Extenisons are archive specific, windows will be zip and all others will be tar.gz.

On Windows:

> ./build.ps1

On Linux / Unix:

$ ./build.sh

You can find the output under artifacts/publish/OmniSharp/<runtime id>/<target framework>/.

The executable is either OmniSharp.exe or OmniSharp.

For more details, see Build.

Add the following setting to your User Settings or Workspace Settings.

{
  "omnisharp.path": "<Path to the omnisharp executable>"
}

The above option can also be set to:

• "latest" - To consume the latest build from the master branch
• A specific version number like 1.29.2-beta.60

In order to be able to attach a debugger, add the following setting:

{
  "omnisharp.waitForDebugger": true
}

This will print the OmniSharp process ID in the VS Code OmniSharp output panel and pause the start of the server until a debugger is attached to this process. This is equivalent to launching OmniSharp from a command line with the --debug flag.

We have slack room as well. Get yourself invited: here