Skip to content

Releases: dotnet/vscode-csharp

v1.19.0

15 Apr 17:42
c56b14f

Choose a tag to compare

Merge pull request #2989 from akshita31/version_1.19.0

Add the changes for the 1.19.0 release

v1.19.0-beta1

13 Apr 00:52
af7c31f

Choose a tag to compare

v1.19.0-beta1 Pre-release
Pre-release
Merge pull request #2979 from akshita31/rename_project_id_and_change_…

v1.18.1

11 Apr 17:06
12bdde3

Choose a tag to compare

Merge pull request #2977 from rchande/omnisharp-1.32.16

Omnisharp 1.32.16; changelog

v1.18.0

26 Mar 15:05
1279c53

Choose a tag to compare

  • Added a csharp.maxProjectFileCountForDiagnosticAnalysis setting to configure the file limit when the extension stops reporting errors for whole workspace. When this threshold is reached, the diagnostics are reported for currently opened files only. This mechanism was available in previous versions, but now can be configured. The default is 1000. (PR: #1877)
  • Added a omnisharp.enableMsBuildLoadProjectsOnDemand setting to load project for files that were opened in the editor. This setting is useful for big C# codebases and allows for faster initialization of code navigation features only for projects that are relevant to code that is being edited._(Contributed by @dmgonch)(PR: #2750)
  • Added initial support for C# 8. (PR: omnisharp-roslyn#1365)
  • Fixed finding references to operator overloads (Contributed by @SirIntruder) (PR: omnisharp-roslyn#1371)
  • Improved handling of files moving on disk (PR: omnisharp-roslyn#1368)
  • Improved detection of MSBuild when multiple instances are available (Contributed by @johnnyasantoss ) (PR: omnisharp-roslyn#1349)
  • Fixed a bug where the "OmniSharp" and "C# log" would steal the editor focus and hinder the user's development flow.(PR: #2828)
  • Improvement in code load times for the extension by using webpack (PR: #2835)
  • Added tasks for "dotnet publish" and "dotnet watch" in the initial asset generation (Contributed by @timheuer ) (PR: #2903)

Debugger

  • Added support for set next statement. Set next statement is a feature that has been available for a long time in full Visual Studio, and this brings the feature to Visual Studio Code. This feature allows developers to change what code is executed next in the target program. For example, you can move the instruction pointer back to re-execute a function that you just ran so you can debug into it, or you can skip over some code that you don't want to execute. To use this feature, move your cursor to the statement you would like to execute next, and either open the editor context menu and invoke 'Set Next Statement (.NET)', or use the keyboard shortcut of Ctrl+Shift+F10 (#1753)
  • Improved responsiveness by making the debugger backend asynchronous and cancelable so that operations (ex: evaluate expression 'xyz') can be aborted on step/go/disconnect (#1215).
  • Added support for pagination of evaluation result children. Before, if an element in the watch/variables/data tip had a large number of child elements, then the first 1,000 children would be calculated up front and no others would be shown. This could be very slow. Now only the first 25 elements are calculated and there is a '[More]' node to obtain additional values. Note that if you are trying to find a particular element in a large collection it is still best to use Linq (example: myCollection.Where(x => x > 12).ToList()).
  • Added support for showing return values in the variables window (#859).
  • Fixed evaluating string functions with interpretation in .NET Core 2.1+. Evaluation uses interpretation for conditional breakpoints, evaluating methods that take a lambda, etc (#2683).
  • Many small improvements to launch.json/tasks.json generation. Highlights include a selection dialog if the workspace contains multiple launchable projects, a few simplifications to reduce the number of fields in the default launch.json, and switching the 'problem matcher' for build tasks. (PR: #2780)
  • Updated the default symbol cache directory to match other .NET Tools (#2797).

v1.18.0-beta11

22 Mar 17:18
2edb841

Choose a tag to compare

v1.18.0-beta11 Pre-release
Pre-release
Merge pull request #2925 from akshita31/dirname_false

Make razor work for the webpacked extension

v1.18.0-beta10

15 Mar 04:00
6082b08

Choose a tag to compare

v1.18.0-beta10 Pre-release
Pre-release
Merge pull request #2909 from akshita31/change_log

Add changelog and update beta 10

v1.18.0-beta9

14 Mar 23:14
41c5a05

Choose a tag to compare

v1.18.0-beta9 Pre-release
Pre-release
Merge pull request #2906 from akshita31/acquisition_succeed

Split the acquisition event into two

v1.18.0-beta8

28 Feb 19:25
9459aa0

Choose a tag to compare

v1.18.0-beta8 Pre-release
Pre-release
  • Updated to Roslyn 3.0.0-beta4-19126-05 to match VS 16.0p4 (#1413, PR: #1414)
  • Added support for reading C# 8.0 NullableContextOptions from csproj files (#1396, PR: #1404)

v1.18.0-beta7

06 Feb 20:37
8257f7f

Choose a tag to compare

v1.18.0-beta7 Pre-release
Pre-release

Improvement in code load times for the extension by using webpack (PR: #2835)

v1.18.0-beta6

01 Feb 00:18
656c182

Choose a tag to compare

v1.18.0-beta6 Pre-release
Pre-release

Includes updated packages for the extension dependencies.
The update to rxjs 6 will significantly reduce the bundle size
PR: #2830