Releases: OmniSharp/omnisharp-roslyn
Releases · OmniSharp/omnisharp-roslyn
v1.33.0
- Added support for
.editorconfig
files to control formatting settings, analyzers, coding styles and naming conventions. The feature is currently opt-into and needs to be enabled using OmniSharp configuration{ "FormattingOptions": { "EnableEditorConfigSupport": true } }
- Analyzers improvements
- Dynamically loaded / modifiable rulesets instead without full restart on omnisharp after every change
- Reanalyze updated projects
- Built-int Roslyn diagnostics can be controlled by rulesets even when analyzers are not enabled
- Faster analysis since project isn't updated every time
- When project is restored it is re-analyzed with correct dependencies
- Added support for various renaming options - renaming any symbol can now propagate to comments or strings, and renaming a method symbol can also rename its overloads. They can be set via OmniSharp configuration, such as
omnisharp.json
file (they are disabled by default){ "RenameOptions": { "RenameInComments": true, "RenameOverloads": true, "RenameInStrings": true } }
- Fixed a regression on declaration name completion.
- Update to Roslyn
3.2.0-beta4-19326-12
. - Added snippets support in LSP mode.
- Fixed renaming in LSP mode.
v1.32.20
v1.32.19
- Updated to Roslyn
3.1.0-beta4-19251-02
(PR: #1479) - Shadow copy Roslyn analyzers in order to not lock them (#1465, PR: #1474)
- Fixed logging output for OmniSharp HTTP server (#1466, PR: #1456)
- Fixed OmniSharp hanging on wildcard Nuget package references (omnisharp-vscode#3009, PR: #1473)
- OmniSharp now uses correct 4.7.2 framework sku to prompt for installation of .NET 4.7.2 if missing (#1468, PR: #1469)