BinlogInsights

Compare two MSBuild builds and report differences using binlog-insights MCP tools. Use when comparing CI vs local builds, before/after a change, different build configurations, or migrating build systems (e.g., CoreXT to stock MSBuild). Also triggers for build diff, environment differences, and package version mismatch.

Investigate MSBuild build failures using binlog-insights MCP tools. Use when a dotnet build or msbuild command fails, NuGet restore fails, or you see errors like CS0246, NU1101, MSB3644, MSB4019. Also triggers for missing type, missing package, import not found, and SDK resolution issues.

Analyze MSBuild build performance and find bottlenecks using binlog-insights MCP tools. Use when a build is slow, you need to optimize build times, or identify expensive projects, targets, tasks, or Roslyn analyzers. Also triggers for build duration, build speed, and compilation time.

Install or update the binlog-insights MCP server tool. Use when binlog-insights-mcp is not found, tool installation fails due to NuGet configuration, or the tool needs updating. Also triggers for dotnet tool install errors, NuGet source problems, and MCP server not starting.