Start Debugging

Tag: msbuild

18 posts · Page 2 of 2

2026-06-20 dotnet msbuild mcp

The Binlog MCP Server Lets an AI Read Your MSBuild Logs

Microsoft shipped Microsoft.AITools.BinlogMcp on 2026-06-17, an MCP server that exposes 15 tools so Claude or Copilot can diagnose build failures and slow targets straight from a .binlog file.

2026-05-24 dotnet nuget msbuild

Independently Releasing Multiple NuGet Packages with MinVer + Trusted Publishing

One repo, three NuGet packages, independent versions. Per-package MinVer tag prefixes, a tag-driven GitHub Actions release that publishes via OIDC trusted publishing (no API key), pinning a cross-package dependency to a real version, and the default-branch gotcha that silently swallows your first tag.

2026-05-12 errors csharp dotnet

Fix: System.IO.FileNotFoundException: Could not load file or assembly in a published app

Runs fine with dotnet run, throws after dotnet publish. The DLL is usually missing from the publish folder, not the runtime. Check deps.json, ProjectReference Private, and trimming.

2026-05-11 errors csharp dotnet

Fix: MSB3027 Could not copy X to Y. Exceeded retry count of 10. Failed

MSB3027 means MSBuild retried a file copy 10 times and a process still held the destination. Kill the locking process, exclude bin/obj from antivirus, or raise CopyRetryCount.

2026-05-11 errors csharp dotnet

Fix: The type or namespace name 'X' could not be found (after adding a project reference)

CS0246 right after a fresh ProjectReference is almost always a TargetFramework mismatch, a stale obj folder, or a missing using directive. Five fixes in order of likelihood.

2026-05-03 blazor blazor-webassembly tailwind-css

How to use Tailwind CSS with Blazor WebAssembly in .NET 11

A complete .NET 11 setup for Tailwind CSS v4 in a Blazor WebAssembly app: standalone CLI (no Node), MSBuild target, @source directives for Razor and CSS isolation files, and a publish pipeline that survives Native AOT.

2026-04-18 dotnet dotnet-11 dotnet-cli

.NET 11 Preview 3: dotnet run -e sets environment variables without launch profiles

dotnet run -e in .NET 11 Preview 3 passes environment variables straight from the CLI and surfaces them as MSBuild RuntimeEnvironmentVariable items.

2026-04-18 dotnet-11 sdk dotnet-cli

dotnet sln finally edits solution filters from the CLI in .NET 11 Preview 3

.NET 11 Preview 3 teaches dotnet sln to create, add, remove, and list projects in .slnf solution filters, so large mono-repos can load a subset without opening Visual Studio.