Skip to content

Move to Microsoft.Build.Framework 18.9.6 and pin StringTools - #71

Merged
einari merged 1 commit into
mainfrom
chore/update-microsoft-build-framework-18.9.6
Aug 14, 2026
Merged

Move to Microsoft.Build.Framework 18.9.6 and pin StringTools#71
einari merged 1 commit into
mainfrom
chore/update-microsoft-build-framework-18.9.6

Conversation

@einari

@einari einari commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Unblocks the daily automated Update Packages workflow, which bumps Microsoft.Build.Framework from 17.11.48 to 18.9.6 and transitively pulls in Microsoft.NET.StringTools at the same version, causing the subsequent dotnet build step to fail with:
    error MSBL001: A PackageReference to the package 'Microsoft.NET.StringTools' at version '18.9.6' is present in this project without ExcludeAssets="runtime" and PrivateAssets="all" set. This can cause errors at run-time due to MSBuild assembly-loading. [Source/Cli/Cli.csproj]
    
  • Bumps Microsoft.Build.Framework to 18.9.6 in Directory.Packages.props (latest stable per NuGet.org) and adds a matching Microsoft.NET.StringTools 18.9.6 PackageVersion entry alongside it.
  • Adds a PackageReference for Microsoft.NET.StringTools with ExcludeAssets="runtime" PrivateAssets="all" next to the existing Microsoft.Build.Framework reference in Source/Cli/Cli.csproj and Source/Cli.Specs/Cli.Specs.csproj, mirroring the pattern Microsoft.Build.Locator's own build target requires (both packages must come from the installed .NET SDK that MSBuildLocator registers, never from the output folder).

Test plan

  • dotnet build (Debug) at repo root — succeeds, 0 warnings, 0 errors
  • dotnet build --configuration Release at repo root (matches CI) — succeeds, 0 warnings, 0 errors
  • dotnet test Source/Cli.Specs/Cli.Specs.csproj --configuration Release — 446/446 passed

🤖 Generated with Claude Code

…anion

The daily Update Packages workflow bumps Microsoft.Build.Framework to
18.x, which transitively pulls in Microsoft.NET.StringTools at the same
version. Microsoft.Build.Locator's build-time target then fails the
build (MSBL001) unless that companion package also carries
ExcludeAssets="runtime" PrivateAssets="all", mirroring the existing
Microsoft.Build.Framework reference.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@einari
einari merged commit dbdf887 into main Aug 14, 2026
1 check passed
@einari
einari deleted the chore/update-microsoft-build-framework-18.9.6 branch August 14, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant