Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Directory.Packages.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@
_ValidateBundledSdkFeatureVersions target (in Directory.Build.targets) fails the build if
the two drift apart. -->
<AspireHostingTestingVersion>13.4.6</AspireHostingTestingVersion>
<MicrosoftBuildVersion>17.11.48</MicrosoftBuildVersion>
<MicrosoftBuildVersion>18.9.6</MicrosoftBuildVersion>

@github-actions github-actions Bot Aug 12, 2026

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>

<MicrosoftCodeAnalysisVersion>3.11.0</MicrosoftCodeAnalysisVersion>
<MicrosoftCodeAnalysisVersionForTests>4.10.0</MicrosoftCodeAnalysisVersionForTests>
<MicrosoftCodeAnalysisVersionForSourceGen>4.8.0</MicrosoftCodeAnalysisVersionForSourceGen>
Expand Down
Loading