Skip to content

Releases: dotnet/vscode-csharp

v1.15.0-beta1

26 Feb 20:59
e2a191f

Choose a tag to compare

v1.15.0-beta1 Pre-release
Pre-release

Debugger

  • Adds support for Source Link, Symbol Servers and other more advanced symbol options (#373)
  • Adds launch.json option to suppress Just-In-Time compiler optimizations.
  • Due to the previous two items and work from the .NET Team, it is now possible to easily debug into ASP.NET itself in projects running against .NET Core 2.1 preview 1. Support for debugging into all the managed code in .NET Core will come in future .NET Core 2.1 builds. Instructions are in the wiki.

v1.14.0

14 Feb 21:48
73e16a7

Choose a tag to compare

What's New in 1.14

C# Language Support

Debugger

  • Fixes symbol loading while debugging apps running under .NET Core 2.1 (ex: netcoreapp 2.1) on Linux and macOS
  • Fixes debug console message encoding issue on Windows (#1775).
  • Adds support for extracting source files embedded in PDBs. See the C# EmbeddedFiles feature for more information.
  • Adds preliminary support for Linux ARM debugging

Editor

Project System

Task Generation

Misc

v1.14.0-beta5

14 Feb 00:13
51d0d66

Choose a tag to compare

v1.14.0-beta5 Pre-release
Pre-release
  • Fixed duplicate errors in error list (#1830, PR:#1107)

v1.14.0-beta4

07 Feb 17:35
456d2bc

Choose a tag to compare

v1.14.0-beta4 Pre-release
Pre-release

C# Language Support

Editor

Project System

Task Generation

Misc

v1.14.0-beta3

03 Feb 00:27
f83cbb3

Choose a tag to compare

v1.14.0-beta3 Pre-release
Pre-release

Debugger

  • Fixes symbol loading while debugging apps running under .NET Core 2.1 (ex: netcoreapp 2.1) on macOS
  • Adds support for extracting source files embedded in PDBs. See the C# EmbeddedFiles feature for more information.

v1.14.0-beta2

28 Nov 21:04
47d9285

Choose a tag to compare

v1.14.0-beta2 Pre-release
Pre-release

Debugger

  • Fixes symbol loading while debugging apps running under .NET Core 2.1 (ex: netcoreapp 2.1) on Linux
  • Fixes debug console message encoding issue on Windows (#1775).
  • Adds preliminary support for Linux ARM debugging

v1.14.0-beta1

13 Nov 19:22
a81f872

Choose a tag to compare

v1.14.0-beta1 Pre-release
Pre-release

Editor

Project System

v1.13.1

13 Nov 17:48
a6927e0

Choose a tag to compare

v1.13.0

07 Nov 20:40
b7f067a

Choose a tag to compare

What's New in 1.13

Cake

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

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

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)

v1.13.0-beta5

06 Nov 21:24
dc32557

Choose a tag to compare

v1.13.0-beta5 Pre-release
Pre-release

Debugger

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

Project System

  • 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 Unit Test debugging with VS Code 1.18. (#1800)