Releases: dotnet/vscode-csharp
Releases · dotnet/vscode-csharp
v2.6.24
Changes in 2.6.24
- Update Roslyn version to 4.9.0-1.23506.7 (PR: #6447)
- Fix various issues with project loading and allow fallbacks to .NET framework msbuild (PR: #70240)
- Fix some Razor colorization issues (PR: #6502)
- Fire telemetry if Razor buffers get out of sync, and recover from same (PR: #6494)
- Update OmniSharp to 1.39.10 (PR: #6491)
- Add RazorComplier EA to support razor generators (PR: omnisharp-roslyn#2572)
- Add Kind parameter to InlayHint (PR: omnisharp-roslyn#2570)
- Do not include commit characters if the typed span is empty (PR: omnisharp-roslyn#2569)
- Update Roslyn to version 4.9.0-1.23504.3 (PR: omnisharp-roslyn#2567)
- Async diagnostics analyzer work queue (PR: omnisharp-roslyn#2351)
- Add InlayHint implementation to OmniSharp.LSP (PR: omnisharp-roslyn#2566)
- Include the project file name when invoking
dotnet build
(PR: omnisharp-roslyn#2565) - feat: ignore diagnostics for generated code (PR: omnisharp-roslyn#2509)
- Update documentation to reflect --stdio flag deprecation (#2439) (PR: omnisharp-roslyn#2554)
- Update Roslyn to version 4.8.0-1.23374.10 (PR: omnisharp-roslyn#2555)
- Use double quote when quoting un script path (PR: omnisharp-roslyn#2553)
- Use core LSP TokenTypes where possible and validate token names (PR: omnisharp-roslyn#2548)
- Add Razor C# semantic tokens support in VS Code (PR: #6489)
- Update Roslyn version to 4.9.0-1.23502.8 (PR: #6447)
- Debugger: Improve the display of various debug configurations and snippets (PR: #6456)
- Initialize Razor even if Razor doc isn't opened yet (PR: #6473)
v2.5.30
v2.5.30
- Add code action fix all support (PR: #6310)
- Update Roslyn version to 4.9.0-1.23502.2 (PR: #6463)
- Update Razor version to 7.0.0-preview.23475.5 (PR: #6449)
- Fix issues with Razor completion (PR: #6441)
- Add option to collect crash dumps on language server crash (PR: #6438)
- Add support for multilaunch for Blazorwasm (PR: #6432)
- Fix issue in Razor new file formatting (PR: #6429)
- Fix issue in debug tests where tests would complete before the debugger attached (PR: #6415)
- Hide certain debugger launch configurations when devkit is installed (PR: #6405)
- Fix issue where build errors were not parsed correctly in the problems list (PR: #6340)
- Update debugger packages to 2.0.3 (PR: #6401)
v2.4.4
v2.3.27
Note: This release is to the regular 'release' channel, and includes the changes in v2.2.10 which were only shipped to the pre-release channel.
Changes Since v2.2.10
- Update Roslyn version to 4.8.0-3.23470.7 (PR: #6408)
- Update NuGet version to fix issues loading projects with .NET 8 RC2 (PR: #70023)
- Update MSBuildLocator version to fix issues loading projects when only .NET 6 is installed (PR: #70038)
- Remove diagnostic source name (PR: #69939)
- Fix fold all regions (PR: #69817)
- Fix escaping and wrapping in hover (PR: #69893)
- Fix error in override completion when containing type does not exist (PR: #69855)
- Fix issues generating assets in Omnisharp (PR: #6380)
- Allow Razor to format new documents via Roslyn (PR: #6329)
- Switch to named pipes for client <-> server communication (PR: #6351)
- Only show clr debugger if on Windows (PR: #6359)
- Update Razor version to 7.0.0-preview.23456.2 (PR: #6304)
- Fixes regression where semantic colors for razor components appear as red
- Make completion complex text edits more robust (PR: #6325)
- Fix dotnet info when the dotnet path contains spaces (PR: #6334)
- Add support for specifying a .runsettings file when using Roslyn LSP (PR: #6265)
- Update Roslyn version (PR: #6265)
- Remove test only files from vsix (PR: #6332)
- Fix override completion when drive letter casing does not match (PR: #6315)
- Allow the server path to be specified by the
DOTNET_ROSLYN_SERVER_PATH
environment variable (PR: #6316)
v2.2.10
Changes Since v2.1.2
- Update Roslyn version
- Includes better support for .NET 8 and .NET Framework-targeting projects (PR: #69616)
- This should fix a number of reports where projects don't have full IntelliSense. .NET Framework projects on Windows should load without errors. .NET Framework targeting projects on Mac and Linux which would use Mono are still processed as if they are .NET Core projects and may not load correctly; support for Mono is coming in a future update.
- Fix issues where some projects fail to load being unable to find NuGet.Frameworks (PR: #69824)
- Includes better support for .NET 8 and .NET Framework-targeting projects (PR: #69616)
- Update Razor to 7.0.0-preview.23455.5 (PR: #6291)
- Fixes issue reading razor.format.enable and other options (PR: dotnet/razor#9240)
v2.1.2
v2.0.436
Changes Since v2.0.416
- Update Roslyn version (PR: #6245)
- Localization additions (PR: #6233, #6233, #6206, #6196)
- Fix specific case where razor formatting no longer worked (PR: #6195)
- Fix quoting bug in extension paths (PR: #6228)
- Fix Razor mapping errors in the log (PR: #6209)
- Add the configuration option for creating binlogs (PR: #6155)
- Update option changes toast to reload window (PR: #6174)
- Update Roslyn version (PR: #6205)
- Bump Razor to 7.0.0-preview.23421.4 (PR: #6195)
v2.0.416
v2.0.413
- Update Roslyn version (PR: #6192)
- Fix dotnet resolver returning incorrect runtime in certain scenarios (PR: #6180)
- Fix issue resolving .NET 7 runtimes from path (PR: #6175)
- Fix URI issue when loading Razor files (PR: #6168)
- Bump Razor to 7.0.0-preview.23417.3 (PR: #6165)
- Fix various textDocument/foldingRange issues (PR: #9134)
- Clarify dotnet path option description (PR: #6164)
- Handle multiple dotnet on path and symlinks (PR: #6152)
- Localize Roslyn options (PR: #6136)
- Show a prompt if we have more than one solution file (PR: #6132)
v2.0.399
2.0.399 extension release