[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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
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

@dependabotdependabotBot commented on behalf of githubAug 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>
@dependabotdependabotBot added .NET dependencies Updates to dependency manifests. labels Aug 12, 2026
CopilotAI balanced review requested due to automatic review settings August 12, 2026 06:44
@dependabotdependabotBot added dependencies Updates to dependency manifests. .NET labels Aug 12, 2026

CopilotAI 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

dependabotBot commented on behalf of githubAug 12, 2026

Copy link
Copy Markdown
ContributorAuthor

Superseded by #10571.

@dependabotdependabotBot closed this Aug 12, 2026
@dependabot
dependabotBot 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.StringTools18.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-actionsgithub-actionsBot 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 ·

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.StringTools18.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 freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesUpdates to dependency manifests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant