Skip to content

[main] Bump Microsoft.Build.Framework from 17.11.48 to 18.9.6 - #10570

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Microsoft.Build.Framework-18.9.6
Closed

[main] Bump Microsoft.Build.Framework from 17.11.48 to 18.9.6#10570
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Microsoft.Build.Framework-18.9.6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 12, 2026

Copy link
Copy Markdown
Contributor

Updated Microsoft.Build.Framework from 17.11.48 to 18.9.6.

Release notes

Sourced from Microsoft.Build.Framework's releases.

18.9.6

What's Changed

18.8.2

What's Changed

18.7.1

What's Changed

18.6.3

What's Changed

18.5.4

What's Changed

18.4.0

What's Changed

18.3.3

What's Changed

18.0.2

What's Changed

17.14.28

What's Changed

17.14.8

What's Changed

Full Changelog: dotnet/msbuild@v17.14.5...v17.14.8

17.14.5

What's Changed

17.14.0-preview-25177-05

Release

What's Changed

Description has been truncated

---
updated-dependencies:
- dependency-name: Microsoft.Build.Framework
  dependency-version: 18.9.6
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Updates to dependency manifests. labels Aug 12, 2026
Copilot AI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabot dependabot Bot added dependencies Updates to dependency manifests. .NET Pull requests that update .NET code labels Aug 12, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot could not run the full agentic suite for this review because it was automatically requested on a bot-authored pull request. Request a review from Copilot under Reviewers to retry with the full agentic suite. Improved support for bot-authored pull requests is coming soon.

Updates the centrally-managed MSBuild package version used across the repo.

Changes:

  • Bumps MicrosoftBuildVersion from 17.11.48 to 18.9.6.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@dependabot @github

dependabot Bot commented on behalf of github Aug 12, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #10571.

@dependabot dependabot Bot closed this Aug 12, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/Microsoft.Build.Framework-18.9.6 branch August 12, 2026 06:46
@github-actions

Copy link
Copy Markdown
Contributor

🔍 Build Failure Analysis

Summary — The build fails on every leg that compiles Microsoft.Testing.Platform.MSBuild for net8.0/net9.0 because this PR bumps Microsoft.Build.Framework, Microsoft.Build.Utilities.Core, and their transitive Microsoft.NET.StringTools dependency to 18.9.6, whose buildTransitive targets now hard-fail (NETStandardCompatError_*) unless the consuming project targets net10.0+.

Root cause: Microsoft.Build.* 18.9.6 drops net8.0/net9.0 support

Microsoft.Testing.Platform.MSBuild.csproj builds for $(SupportedNetFrameworks);netstandard2.0, where SupportedNetFrameworks is net8.0;net9.0 (Directory.Build.props:76). Starting with Microsoft.Build.Framework/Microsoft.Build.Utilities.Core/Microsoft.NET.StringTools 18.9.6, the packages' buildTransitive/netcoreapp2.0/*.targets emit a build-breaking message when the TFM isn't net10.0+:

Microsoft.Build.Framework 18.9.6 doesn't support net8.0 and has not been tested with it. Consider upgrading your TargetFramework to net10.0 or later. You may also set <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the project file to ignore this warning and attempt to run in this unsupported configuration at your own risk.

This fires for both net8.0 and net9.0, for both Microsoft.Testing.Platform.MSBuild.csproj and its Microsoft.Testing.Platform.MSBuild.UnitTests.csproj consumer, and reproduces on every leg that builds these TFMs (Linux Debug/Release, Windows Debug/Release, macOS Debug). Legs that skip this project/TFM combination (macOS Release, one Windows Debug/Release/app-model job) show no errors.

Affected files / errors

  • Directory.Packages.props:30 — bumps MicrosoftBuildVersion to 18.9.6, the version that introduces the TFM gate.
  • src/Platform/Microsoft.Testing.Platform.MSBuild/Microsoft.Testing.Platform.MSBuild.csproj (targets net8.0;net9.0;netstandard2.0) — fails NETStandardCompatError_Microsoft_{NET_StringTools,Build_Framework,Build_Utilities_Core}_net10_0 on both net8.0 and net9.0.
  • test/UnitTests/Microsoft.Testing.Platform.MSBuild.UnitTests/Microsoft.Testing.Platform.MSBuild.UnitTests.csproj — same failure, same TFMs.

Proposed fix

This repository is not yet ready to move its MSBuild-task TFMs to net10.0, so the safest fix is to stay on the last Microsoft.Build.* version series that still supports net8.0/net9.0 rather than accepting 18.9.6. Suggested inline change below pins MicrosoftBuildVersion back to the last known-compatible 17.x/18.0.x release; a maintainer should confirm the exact highest version still supporting net8.0/net9.0 before merging, since this workflow has no network access to query NuGet for the precise cutoff.

Alternatively, if upgrading remains desired, <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> could be added to both affected .csproj files to acknowledge running in an unsupported configuration — but that trades a hard build break for an explicitly-unsupported runtime combination and should be a deliberate, reviewed decision rather than a silent fix.

Secondary, likely unrelated finding: CS0419 ambiguous cref

Every failing leg also reports a CS0419 warning in src/Platform/Microsoft.Testing.Platform/Helpers/System/ITask.cs:27 (Ambiguous reference in cref attribute: 'UnsupportedOSPlatformAttribute'). This line is not touched by this PR's diff and the warning text doesn't reference the bumped package, so it appears to be a pre-existing doc-comment ambiguity independent of this change — flagging it for visibility, but not proposing a fix here since it isn't part of this PR's diff and its build impact (warning vs. actual failure) couldn't be confirmed from the binlog evidence alone.


Build overview
  • Failing legs: 1_0 Linux Debug, 2_0 Linux Release, 5_0 MacOS Debug, 6_0/6_1 Windows Debug, 7_0/7_1 Windows Release — all report the NETStandardCompatError_* target failures plus the CS0419 warning, ending in Build failed.
  • Clean legs (no errors from binlog_errors): 3_0 MacOS Release, 4_0/4_1 Windows application-model acceptance, 6_2 Windows Debug, 7_2 Windows Release — these don't build the affected TFM/project combination in this leg.
  • Failing project: src/Platform/Microsoft.Testing.Platform.MSBuild/Microsoft.Testing.Platform.MSBuild.csproj and its unit-test project, on net8.0 and net9.0.

🤖 Generated by the Build Failure Analysis workflow using (a href="(dev.azure.com/redacted) · commit f2a3977

🤖 Automated content by GitHub Copilot. Generated by the Build Failure Analysis workflow. · auto · 94 AIC · ⌖ 2.1 AIC · ⊞ 11.6K · [◷]( · )

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 Automated content by GitHub Copilot. Generated by the Build Failure Analysis workflow. · auto · 94 AIC · ⌖ 2.1 AIC · ⊞ 11.6K ·

Comment thread Directory.Packages.props
the two drift apart. -->
<AspireHostingTestingVersion>13.4.6</AspireHostingTestingVersion>
<MicrosoftBuildVersion>17.11.48</MicrosoftBuildVersion>
<MicrosoftBuildVersion>18.9.6</MicrosoftBuildVersion>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔧 NETStandardCompatError (net8.0/net9.0)Microsoft.Build.Framework/Microsoft.Build.Utilities.Core/Microsoft.NET.StringTools 18.9.6 gate their buildTransitive targets behind net10.0+, and Microsoft.Testing.Platform.MSBuild.csproj still targets net8.0;net9.0;netstandard2.0. This bump breaks every build leg that compiles that project (see PR comment for the full binlog evidence). Please pin back to the last Microsoft.Build.* release line that still supports net8.0/net9.0 (verify the exact version with a maintainer/NuGet, since this analysis has no network access) rather than accepting 18.9.6 as-is, or explicitly opt in to the unsupported TFM via <SuppressTfmSupportBuildWarnings>true</SuppressTfmSupportBuildWarnings> in the affected projects if the team decides that's acceptable.

Suggested change
<MicrosoftBuildVersion>18.9.6</MicrosoftBuildVersion>
<MicrosoftBuildVersion>17.11.48</MicrosoftBuildVersion>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates to dependency manifests. .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant