RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Pick a date

  1. Sat 16 may
  2. Sun 17 may
  3. Tue 19 may
  4. Wed 20 may
  5. Thu 21 may
  6. Sat 23 may
  7. Sun 24 may
  8. Mon 25 may
  9. Tue 26 may
  10. Wed 27 may
  11. Thu 28 may
  12. Fri 29 may
  13. Sat 30 may
  14. Sun 31 may
  15. Mon 1 jun
  16. Mon 8 jun
  17. Tue 9 jun
  18. Today 10 jun

The Wire · Showcase

MSBUILD FIXES ERROR REPORTING ON OLDER SDKS, DEV-PROXY HITS V3.0.0

By RepoJournal · Filed · About .NET

MSBuild stops lying about missing task hosts on SDK 10.0.x, while dev-proxy ships its biggest update with auth key support for CRUD APIs.

The MSBuild team fixed a long-standing frustration where the MSB4216 error pointed at a file that didn't exist [1]. On SDKs 10.0.x through 10.0.299, the task host launcher falls back to `dotnet.exe MSBuild.dll` when the app host isn't present, but the error message kept referencing `MSBuild.exe` anyway [2]. Developers debugging build failures saw a phantom file path that wasted hours. This is the kind of fix that saves senior engineers from hours of misdirected troubleshooting. Meanwhile, dev-proxy crossed into v3.0.0 territory [3], bringing auth key support for CRUD API skills with full schema updates [4]. The Code Radiator workflow in macios got a critical fix too: the CI was unsetting git's upstream tracking branch mid-build, which broke the PR creation logic in safeoutputs [5]. WinForms added coverage for PropertyGrid component removal tests [6], and the team added GitHub Actions security linting with zizmor [7]. Nothing here breaks your builds, but the MSBuild fix and dev-proxy release are worth noting for teams managing SDK complexity.

Action items

References

  1. [1] Report actual launch path in MSB4216 for Runtime="NET" task host ↗ dotnet/msbuild
  2. [2] Report actual launch path in MSB4216 for Runtime="NET" task host (#13889) dotnet/msbuild
  3. [3] v3.0.0 ↗ dotnet/dev-proxy
  4. [4] Add auth key support for CRUD API to skill. Closes #1663 ↗ dotnet/dev-proxy
  5. [5] [github] Fix Code Radiator: prevent upstream unsetting that breaks safeoutputs PR creation. Fixes #25555. (#25563) dotnet/macios
  6. [6] Add tests for PropertyGrid.OnComponentRemoved ↗ dotnet/winforms
  7. [7] [github] Add zizmor GitHub Actions security linter workflow (#25560) dotnet/macios

FAQ

What changed in .NET on May 29, 2026?
MSBuild stops lying about missing task hosts on SDK 10.0.x, while dev-proxy ships its biggest update with auth key support for CRUD APIs.
What should .NET teams do about it?
If you maintain build infrastructure targeting SDK 10.0.0 to 10.0.299, verify MSBuild error messages now point to actual files • Update dev-proxy references to v3.0.0 in your CRUD API skill configurations • Monitor Code Radiator workflows in macios; upstream unsetting issue now resolved
Which .NET repositories shipped on May 29, 2026?
dotnet/msbuild, dotnet/dev-proxy, dotnet/macios, dotnet/winforms

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.