v1.13.0

What's New in 1.13

Cake

• Added support for *.cake files! (PRs: #1681, omnisharp-roslyn#932) (Contributed by @mholo65)

Debugger

• Improved logic for resolving breakpoints in local functions and lambdas. (#1678)
• When generating a new launch.json file via "start debugging" in a workspace without a launch.json file, the extension now provides the same content as is created with the '.NET: Generate Assets for Build and Debug' command. This takes advantage of a new extensibility point from VS Code. Before the C# extension could only statically provide templates, so, for example, they couldn't have the path to the launchable project. (PR: #1801)

Editor

• Improved completion list behavior when matching substrings. (PRs: #1813, omnisharp-roslyn#990) (Contributed by @filipw)
• Completion list now triggers on SPACE after new. (#146, PR: #1776, omnisharp-roslyn#975)

Navigation

• Fixed issue with Go to Definition where it was not possible to navigate to a definition within the same file if the file was generated from metadata. (PR: #1772) (Contributed by @filipw)
• Improved symbol search behavior when matching substrings. (PR: omnisharp-roslyn#990) (Contributed by @filipw)

Project System

• Significantly changed how MSBuild is located by OmniSharp, resulting in more project types loading properly. (PR: omnisharp-roslyn#988)
• Fixed bug where LangVersion property was not read correctly from project file, blocking C# 7.1 development. (omnisharp-roslyn#961, PR: omnisharp-roslyn#962]) (Contributed by @filipw)
• Fixed issue where signing key was not read correctly from project file, which can result in InternalsVisibleTo not being handled properly. (PR: omnisharp-roslyn#964)
• Fixed long-standing problem with renaming files. (#785, #1792, PR: #1805)
• Fixed problem where the Antlr4.CodeGenerator Nuget package would not generate files during OmniSharp design-time build. (#1822, PR: omnisharp-roslyn#1002)
• Fixed issue where a C# project referencing a non-C# project would cause the referenced project to be loaded (causing OmniSharp to potentially treat it as C#!). (#371, #1829, PR: omnisharp-roslyn#1005)

Testing

• Fix error that occurs when running or debugging tests with latest xUnit 2.3.0 builds. (#1733, omnisharp-rolsyn#944, PR: omnisharp-roslyn#945, #1749)
• Fix issue causing NUnit tests not to work when running or debugging tests. (#1615, PR: #1760). (Contributed by @dgileadi)
• Pass --no-restore when invoking dotnet build to ensure that implicit restore does not run, making the build and the test run a bit faster. (omnisharp-roslyn##942, PR: omnisharp-roslyn#945)
• Fix Unit Test debugging with VS Code 1.18. (#1800)

Other Updates and Fixes

• If Mono 5.2.0 or greater is installed, OmniSharp will be launched on that rather than the local Mono runtime that it carries with it. This allows, more Mono and Xamarin projects to load properly and improves OmniSharp performance (since it can run on Mono AOT'd binaries). (#1779, PR: #1789)
• Support added for launching OmniSharp on folders and solutions across multi-root workspaces. (#1762, PR: #1806)
• Added csharp.referencesCodeLens.enabled and csharp.testsCodeLens.enabled options to allow disabling/enabling for the 'references' and 'run/debug test' code lenses independently. (#1570, #1807, PRs: #1781, #1809)