v1.22.0
If you enable our semantic highlighting support then, be sure to try out our new Visual Studio 2019 Light and Dark themes. TypeScript looks great in it too!
NOTE: For semantic highlighting ensure that editor.semanticHighlighting.enabled and csharp.semanticHighlighting.enabled are set to true.
Changes
- Add setting for enabling go to decompilation (PR: #3774)
- Add experimental Semantic Highlighter
csharp.semanticHighlighting.enabled(#3565, PR: #3667 - Add commands for Run and Debug Tests in Context (PR: #3772, PR: omnisharp-roslyn/#1782)
- Do not add references CodeLens to Dispose methods (#3243, PR: #3780)
- Add Visual Studio 2019 themes with semantic colors (PR: #3790)
- Added support for
WarningsAsErrorsin csproj files (PR: omnisharp-roslyn/#1779) - Added support for
WarningsNotAsErrorsin csproj files (omnisharp-roslyn/#1681, PR: #1784) - Improved MSBuild scoring system (omnisharp-roslyn/#1783, PR: omnisharp-roslyn/#1797)
- Updated OmniSharp.Extensions.LanguageServer to
0.14.2to fix synchronisation (PR: omnisharp-roslyn/#1791) - Add test discovery and NoBuild option to test requests (PR: omnisharp-roslyn/#1719)
- Updated Razor support
- Enable Semantic Highlighting for Razor TagHelpers and Blazor components (aspnetcore#21713)
- Directive and TagHelper Attribute Completions are now committed contextually with
=,:andcommit characters. (aspnetcore#21485) - Removed TagHelper attribute completion snippet support as we felt the typing experience was superior without it.
- Add support for Blazor WebAssembly-specific debug adapter (dotnet/aspnetcore-tooling#1885)