Bump Microsoft.Build packages to 18.6.* and upgrade to net10.0#26
Merged
coderpatros merged 2 commits intoMay 16, 2026
Merged
Conversation
…o net10.0 Updates Microsoft.Build.Utilities.Core and Microsoft.Build.Framework from 17.11.* to 18.6.*, and upgrades all project TargetFrameworks from net8.0 to net10.0 (required by MSBuild 18.6.x packages). Also updates the hardcoded assembly path in the build targets file to match the new TFM output folder. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
coderpatros
approved these changes
May 16, 2026
TestProjectHelper.cs was resolving the task DLL from the net8.0 output folder, causing integration tests to fail with MSB4062. SampleApp.csproj had the same stale path. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
coderpatros
approved these changes
May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Microsoft.Build.Utilities.Corefrom17.11.*to18.6.*(same change as Bump Microsoft.Build.Framework and Microsoft.Build.Utilities.Core #25)Microsoft.Build.Frameworkfrom17.11.*to18.6.*(same change as Bump Microsoft.Build.Framework and Microsoft.Build.Utilities.Core #25)TargetFrameworkfromnet8.0tonet10.0across all projects — MSBuild 18.6.x packages require net10.0 and emit build warnings when targeting net8.0build/CycloneDX.MSBuildTask.targetsfromtasks/net8.0/totasks/net10.0/to match the new output folderWhy net10.0?
After bumping the MSBuild packages, the build emits 12 warnings like:
Since
TreatWarningsAsErrorsis not set to false anywhere, these warnings block a clean build. Upgrading the target framework to net10.0 (already installed on this machine and in global.json) resolves all of them.Test plan
dotnet buildpasses with 0 warnings and 0 errorsdotnet test test/CycloneDX.MSBuildTask.Tests)dotnet test test/CycloneDX.MSBuildTask.IntegrationTests)🤖 Generated with Claude Code