Releases: dotnet/vscode-csharp
Releases Β· dotnet/vscode-csharp
v2.23.14
Changes in 2.23.14
- Rename RazorComponentAttribute semantic token to razorComponentAttribute (PR: #6867)
- Drop win32-ia32 platform support (PR: #6983)
- Fix some issues with casing when comparing Razor files (PR: #6974)
- Do not timeout on connecting to the server if waitForDebugger is set (PR: #6969)
- Bump Razor and update changelog (PR: #6965)
- Update Debugger Packages to v2.19.17 (PR: #6958)
v2.22.5
v2.23.2
Changes in 2.23.2 (Prerelease)
- Updated debugger to fix .NET debugging break with searchNuGetOrgSymbolServer enabled (PR: #6937)
- Update Razor to add formatting option to force open brace onto the next line after a @code or @functions block (PR: #10018)
v2.22.3
Changes in v2.22.3 (since 2.19.13)
- Update Roslyn to run on .NET 8 (PR: #6920)
v2.22.2
2.19.13
Changes in 2.19.13 (Prerelease)
- Fix
Attribute
snippet (PR: #6879) - Add grammar support for new Razor directives: rendermode, preservewhitespace and typeparam (PR: #6887)
- Ensure failures to connect to the named pipe are propagated (PR: #6881)
- Update Razor to 7.0.0-preview.24079.3 (PR: #6841)
- Fix an issue with component hover not showing enough information (PR: dotnet/razor#9862)
v2.18.16
v2.18.15
v2.17.7
v2.15.30
Changes in 2.15.30
- Update Roslyn to 4.10.0-1.24058.1 (PR: #6791)
- Fix error when a source generated file was present in find references or go to definition requests (PR: #71395)
- Remove usages of incorrectly licensed library (Microsoft.VisualStudio.LanguageServer.Protocol) for serialization of LSP json messages (PR: #68990)
- Add custom Roslyn serialization code for LSP json messages (PR: #71141)
- Use named executables for the language server process on Windows and Linux (PR: #71007)
- Add back LSP request telemetry in CLaSP queue (PR: #71157)
- Fix command enablement by using specific activation contexts for O#, Roslyn standalone, and Roslyn devkit (PR: #6782)
- Update Razor to 7.0.0-preview.23627.2 (PR: #6770
- Fixed issue where Razor trace level was ignored. New
razor.server.trace
setting created that is not ignored (PR: dotnet/razor#9745)
- Fixed issue where Razor trace level was ignored. New
- Update OmniSharp to 1.39.11 (PR: #6771)
- Fix loading AspNetCore projects by shipping the AspNetCore EA library
- Update SDKs and dependencies (omnisharp-roslyn/#2586, PR: omnisharp-roslyn/#2588)
- Updated to latest dotnet-script 1.5.0 (PR: omnisharp-roslyn/#2585)
- Update checkForDevCert aka.ms link (PR: #6769)
- Support debug apps running under mono runtime using vsdbg (PR: #6752)
- Update debugger to 2.9.1 (PR: #6765)
- Remove check for projectPath for resolveDebugConfiguration (PR: #6754)