Skip to content
master
Go to file
Code

Latest commit

* LSP: fix performance of the textDocument/codeAction request

This improves performance of codeAction request on large codes base
quite a bit by making the response from textDocument/codeAction to be more
lightweight. This is accomplished by adding a separate command handler for
"omnisharp/executeCodeAction" that actually sends the changes to client
with "workspace/applyEdit".

* Update CHANGELOG.md

* Updated to use new execute command logic.  Added unit tests to ensure funcitonality is working as expected

Co-authored-by: David Driscoll <david.driscoll@gmail.com>
96600de

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

README.md

omnisharp-roslyn

Build Status

Introduction

OmniSharp is a .NET development platform based on Roslyn workspaces. It provides project dependencies and C# language services to various IDEs and plugins.

OmniSharp is built with the .NET Core SDK on Windows and Mono on OSX/Linux. It targets the net472 target framework. For platforms other than Windows, OmniSharp ships with an embedded Mono which is based on version 5.18.0, includes MSBuild 16.3.0 and is provisioned during the build script. If Mono is globally installed on the system, OmniSharp will prefer it over the embedded version, however version >=6.4.0 is required (the lowest version with at least MSBuild 16.3.0).

For Arch Linux users, you need package msbuild-stable (>= 16.3).

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 also https://github.com/OmniSharp/omnisharp-roslyn/issues/1202#issuecomment-421543905 .

What's new

See our change log for all of the updates.

Using OmniSharp

OmniSharp ships in two flavors:

  • Stdio server
  • HTTP server

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)
  • Extensions 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.

Configuration

OmniSharp provides a rich set of hierarchical configuration options, controlled via startup arguments, environment variables and omnisharp.json file. For more details please visit the Configuration Options section of the wiki.

Help wanted!

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

License

Copyright © .NET Foundation, and contributors.

OmniSharp is provided as-is under the MIT license. For more information see LICENSE.

Code of Conduct

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. For more information see the .NET Foundation Code of Conduct.

Contribution License Agreement

By signing the CLA, the community is free to use your contribution to .NET Foundation projects.

.NET Foundation

This project is supported by the .NET Foundation.

You can’t perform that action at this time.