OmniSharp based on roslyn workspaces
C# Other
Switch branches/tags
Clone or download
Latest commit 5b00d66 Aug 14, 2018
Permalink
Failed to load latest commit information.
.vscode Add restore task for VS Code Sep 14, 2017
build Update xUnit to 2.4.0 release Jul 23, 2018
doc added note about plugins Apr 3, 2016
mono-packaging Add packaging scripts for embedded Mono and MSBuild bits Aug 6, 2018
scripts Add packaging scripts for embedded Mono and MSBuild bits Aug 6, 2018
src Add support for Miscellaneous Files (#1252) Aug 13, 2018
test-assets Add support for Miscellaneous Files (#1252) Aug 13, 2018
tests Add support for Miscellaneous Files (#1252) Aug 13, 2018
tools Update xUnit to 2.4.0 release Jul 23, 2018
.editorconfig Added yml configuration for indent, updated indent in appveyor. Fixed… Jan 25, 2018
.gitattributes Force LF EOL for sh scripts Oct 25, 2017
.gitignore Initial tests for Cake handlers. Oct 10, 2017
.lgtm making approvals currently set to 1, as well as let :shipit: work because wh… Apr 29, 2016
.travis.yml Use latest az tools installation methodology Jun 12, 2018
BUILD.md Fix build on CentOS 7 Oct 18, 2017
CHANGELOG.md Add changelog update Aug 14, 2018
CONTRIBUTING.md Update CONTRIBUTING.md Oct 25, 2017
Directory.Build.props clean up Jun 18, 2018
Directory.Build.targets clean up Jun 18, 2018
GitVersion.yml Added azcopy for appveyor Dec 12, 2017
NuGet.Config Remove cli-deps from NuGet.config Apr 6, 2018
OmniSharp.sln Add support for Miscellaneous Files (#1252) Aug 13, 2018
README.md Merge branch 'master' into update/extensions-2.1.0 Jul 16, 2018
appveyor.yml Futher build performance improvements Apr 11, 2018
blobstring.txt.enc Add blob connection info Dec 8, 2017
build.cake Add packaging scripts for embedded Mono and MSBuild bits Aug 6, 2018
build.cmd Fix build.cmd to launch powershell with '-NoProfile' flag Apr 17, 2017
build.json Add packaging scripts for embedded Mono and MSBuild bits Aug 6, 2018
build.ps1 Futher build performance improvements Apr 11, 2018
build.sh Further updates to the build script to ensure that we build Debug by … Apr 6, 2018
global.json Updated all dependendices to .net core 2.1 Jun 30, 2018
license.md Create license.md Jan 5, 2015
omnisharp.json Update omnisharp.json to stop trying to process project.json files Apr 6, 2017
travis_rsa.enc Added new omnisharp_bot key Nov 27, 2015

README.md

omnisharp-roslyn

Mono Build Status Windows Build status

Introduction

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 net461 target framework. OmniSharp requires mono (>=5.2.0) if it is run on a platform other than Windows.

For Arch Linux users, need package msbuild-stable (>= 15.0)

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.

What's new

See our change log for all of the updates.

Using the latest OmniSharp-Roslyn with VS Code

Prerelease Versions

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.

Building

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.

VS Code

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.

Help wanted!

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