Repository navigation
chore: target .NET 10 and .NET 11 for the schema tool (v4.4.0) - #64
Merged
Merged
Conversation
ModernUOSchemaGenerator was net10.0 only, so it could not launch on a machine with only the .NET 11 runtime. The tool package now carries tools/net10.0 and tools/net11.0 and dotnet picks the matching one. The generator and annotations stay netstandard2.0; they are bumped to 4.4.0 to keep the three packages versioned together. The tests run on both frameworks, and CI installs both SDKs. Publishing uses .NET 11. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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
ModernUOSchemaGeneratortargetsnet10.0;net11.0. Before, it was net10.0 only, sodotnet tool runcould not start it on a machine with only the .NET 11 runtime, such as a CI runner set up from a .NET 11global.json. The package now carriestools/net10.0andtools/net11.0, and dotnet picks the one that matches the installed runtime.netstandard2.0and need no change for .NET 11. All three packages move to 4.4.0 so their versions stay in step.Note: the tool already handled net11 projects before this change. Roslyn's out-of-process BuildHost rolls forward to the newest runtime. Only the tool's own process was tied to .NET 10.
Testing
dotnet test -c Release: 130/130 on net10.0 and 130/130 on net11.0.main(17, all pre-existing RS2008/NU5128).tools/net11.0and ran on the 11.0.0 runtime. Both projects migrated cleanly, with no schema diff.