microsoft / ConcordExtensibilitySamples

Visual Studio Debug Engine Extensibility Samples
Other
121 stars 50 forks source link

Announcement: New releases of C# vsdbg #90

Open gregg-miskelly opened 1 year ago

gregg-miskelly commented 1 year ago

Summary

This issue will be the announcement page for new releases of vsdbg for C# debugging. When new releases happen https://aka.ms/getvsdbgsh and https://aka.ms/getvsdbgps1 are updated to point at the new release.

gregg-miskelly commented 1 year ago

Today we are announcing the release of vsdbg 17.6.10401.3, this includes the features in vsdbg to match Visual Studio 17.6. These bits also shipped with VS Code C# extension through version 1.25.7 of the 'coreclr-debug' package.

gregg-miskelly commented 1 year ago

vsdbg 17.6.10606.1 was released today. This is a hotfix that contains only the fix for #94. It will also ship with the next version of the VS Code C# Extension (version 1.25.8 of the debugger).

gregg-miskelly commented 1 year ago

vsdbg 17.7.10808.2 was released today. This includes any VS 17.7 bug fixes, plus the following changes:

gregg-miskelly commented 8 months ago

It has come to my attention that we failed to announce our last release. Sorry for the delay on this.

11/29/2023: vsdbg 17.8.11123.1 was released. This updates vsdbg to the same code as was shipped in VS 17.8.

gregg-miskelly commented 8 months ago

vsdbg 17.8.11212.2 was released today. This fixes the string truncation issue (see dotnet-vscode#6496) for vsdbg. Previously we only shipped the fix for the C# extension.

gregg-miskelly commented 6 months ago

vsdbg 17.10.20204.2 was released today. This contains various bug fixes that match up with VS 17.9, and also addresses https://github.com/dotnet/vscode-csharp/issues/6828.

gregg-miskelly commented 6 months ago

vsdbg 17.10.20209.7 was release today. This is a hotfix release with a single bug fix - previous versions of Visual Studio contained a bug in their handling of telemetry output events if the event arrived during shutdown. This works around the problem by not sending such events.