Skip to content

Releases: dotnet/vscode-csharp

v1.23.15-beta1

03 Aug 16:09
Compare
Choose a tag to compare
v1.23.15-beta1 Pre-release
Pre-release
  • Restore launch target for workspace root when no solution present (#4691, PR: #4695)

v1.23.14

28 Jul 19:01
Compare
Choose a tag to compare

v1.23.14-beta3

27 Jul 20:55
debbdc6
Compare
Choose a tag to compare
v1.23.14-beta3 Pre-release
Pre-release

v1.23.14-beta2

21 Jul 17:30
b45aa77
Compare
Choose a tag to compare
v1.23.14-beta2 Pre-release
Pre-release
  • Bump minimum required version of VS Code (PR: #4664)
  • Update OmniSharp version to 1.37.13
  • Debugger changes:
    • Added support for win10-arm64 debugging (#3006, PR: #4672)
  • Fix typo in windows arm64 package. (PR: #4675, PR: #4676)

v1.23.14-beta1

21 Jul 00:19
f654921
Compare
Choose a tag to compare
v1.23.14-beta1 Pre-release
Pre-release
  • Bump minimum required version of VS Code (PR: #4664)
  • Update OmniSharp version to 1.37.13
  • Debugger changes:
    • Added support for win10-arm64 debugging (#3006, PR: #4672)

v1.23.13

12 Jul 22:58
27d6566
Compare
Choose a tag to compare

v1.23.12

26 May 04:26
Compare
Choose a tag to compare

v1.23.12-beta1

15 Apr 00:15
d178594
Compare
Choose a tag to compare
v1.23.12-beta1 Pre-release
Pre-release

Debugger changes:

  • Added support for osx-arm64 debugging (#4390)
  • Added support for exception conditions. See documentation for more information (#4356).
  • Fixed an issue with character encoding for multi-byte characters written to the debug console (#4398)

v1.23.11

09 Apr 20:16
Compare
Choose a tag to compare

Known Issues in 1.23.11

  • For Mono-based development (e.g. Unity) that requires full .NET framework, you need to set "omnisharp.useGlobalMono": "always". The current value of "auto" will remain "never" until Mono upgrades their bundled MSBuild version.
  • After selecting a solution filter (*.slnf) from the project selector, the solution's name will be displayed in the status bar instead of the filter's.
  • Known limitations with the preview Razor (cshtml) language service to be addressed in a future release:
    • Only ASP.NET Core projects are supported (no support for ASP.NET projects)
    • Error squiggles misaligned for expressions near the start of a new line
    • Emmet based abbreviation expansion is not yet supported (See note in readme for how to enable through your settings.json)
  • There currently is no completion support for package references in csproj files. (#1156)
  • Renaming symbol fails within a file that had recently been renamed without saving changes.
    • As a workaround, make an edit within the file before using Rename Symbol.

Changes

  • Move the global Mono check to the correct place (#4489, PR: #4492)

v1.23.10

08 Apr 21:50
7c85228
Compare
Choose a tag to compare

Known Issues

  • For Mono-based development (e.g. Unity) that requires full .NET framework, you need to set "omnisharp.useGlobalMono": "always". The current value of "auto" will remain "never" until Mono upgrades their bundled MSBuild version.
  • After selecting a solution filter (*.slnf) from the project selector, the solution's name will be displayed in the status bar instead of the filter's.
  • Known limitations with the preview Razor (cshtml) language service to be addressed in a future release:
    • Only ASP.NET Core projects are supported (no support for ASP.NET projects)
    • Error squiggles misaligned for expressions near the start of a new line
    • Emmet based abbreviation expansion is not yet supported (See note in readme for how to enable through your settings.json)
  • There currently is no completion support for package references in csproj files. (#1156)
  • Renaming symbol fails within a file that had recently been renamed without saving changes.
    • As a workaround, make an edit within the file before using Rename Symbol.

Changes