Releases: dotutils/vscode-binlog-analyzer
Releases · dotutils/vscode-binlog-analyzer
v0.10.24 — Fix migration from old AITools.BinlogMcp package
Fixed
- Migration from old AITools.BinlogMcp package — kill running binlog-mcp processes before uninstalling the old package to prevent ''DotnetToolSettings.xml not found'' and access-denied errors during migration.
- Replaced deprecated wmic — process discovery now uses PowerShell Get-Process, which works on all Windows versions including Windows 11+.
What's Changed
- Switch AITools.BinlogMcp feed from dotnet-eng to dotnet-tools by @YuliiaKovalova in #10
- Fix multi-binlog crashes in timeline, tree view, and diagnostics by @YuliiaKovalova in #11
- Rename MCP package to Microsoft.AITools.BinlogMcp by @YuliiaKovalova in #12
Full Changelog: v0.10.20...v0.10.24
v0.10.20 — Auto-migration on activation
Auto-migration from BinlogInsights.Mcp to AITools.BinlogMcp now runs on extension activation, not just on binlog load.
Full Changelog: v0.10.19...v0.10.20
Full Changelog: v0.10.19...v0.10.20
v0.10.19 — Switch to AITools.BinlogMcp
What's Changed
Switched the underlying MCP server from BinlogInsights.Mcp (nuget.org) to AITools.BinlogMcp from the dotnet-eng feed.
Highlights
- Automatic migration — existing BinlogInsights.Mcp users are auto-migrated on extension update
- Full backward compatibility — both old and new MCP response formats handled
- Bug fixes — stale binlog_file injection, consistent project counts, correct task parameter names
Or just install the extension — it auto-installs the MCP server on first use.
Full Changelog: v0.10.18...v0.10.19
What's Changed
- Switch MCP server from BinlogInsights.Mcp to AITools.BinlogMcp by @YuliiaKovalova in #8
- v0.10.19: Switch MCP server to AITools.BinlogMcp by @YuliiaKovalova in #9
Full Changelog: v0.10.18...v0.10.19
v0.10.18
What's Changed
- Copilot/knowledge gap fixes by @YuliiaKovalova in #4
- Copilot/knowledge gap fixes by @YuliiaKovalova in #5
- Bump version to 0.10.17 by @YuliiaKovalova in #6
- Add telemetry for stuck cases by @JanKrivanek in #7
New Contributors
- @YuliiaKovalova made their first contribution in #4
- @JanKrivanek made their first contribution in #7
Full Changelog: v0.10.16...v0.10.18
v0.10.18
What's Changed
- Copilot/knowledge gap fixes by @YuliiaKovalova in #4
- Copilot/knowledge gap fixes by @YuliiaKovalova in #5
- Bump version to 0.10.17 by @YuliiaKovalova in #6
- Add telemetry for stuck cases by @JanKrivanek in #7
New Contributors
- @YuliiaKovalova made their first contribution in #4
- @JanKrivanek made their first contribution in #7
Full Changelog: v0.10.16...v0.10.18
v0.10.17
Full Changelog: v0.10.16...v0.10.17
v0.10.16
Full Changelog: v0.10.15...v0.10.16
v0.10.15
Full Changelog: v0.10.14...v0.10.15
v0.10.14
New
- Wall-clock time in comparison report — shows actual elapsed build time alongside cumulative target time
- Tooltips on timeline — explain cumulative vs wall-clock time for targets/tasks
Fixed
- tool_calls serialization error — eliminated ToolCallPart/ToolResultPart in message history; tool results passed as plain text
- Binlog loaded too early — 15s file stabilization prevents loading incomplete binlog
- New chat on binlog load — avoids stale tool-call history from previous sessions
- History with tool calls — response turns containing tool calls skipped from history replay
Full Changelog: v0.10.13...v0.10.14
v0.10.13
Fixed
- Root cause fix for tool_calls error — eliminated ToolCallPart/ToolResultPart serialization. Tool results now passed as plain text.
- Binlog loaded too early — 15s stabilization check.
- New chat on binlog load — avoids stale tool-call history.