Feature/dotnet 10 upgrade #660
Draft
Conversation
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
- Updated global.json SDK version from 8.0.201 to 10.0.101 - Updated all 27 .csproj files from net8.0 to net10.0 - Verified build succeeds - Verified all 344 unit tests pass Signed-off-by: Dan Benitah <bdanuw@gmail.com>
- Updated all Dockerfiles to use .NET 10 base images - Updated GitHub Actions workflows to use .NET 10 SDK - Updated DLL path in workflow to net10.0 Signed-off-by: Dan Benitah <bdanuw@gmail.com>
- Updated launch.json debug paths to net10.0 - Updated GSF.CarbonAware package lib paths to net10.0 - Updated client generation scripts to target net10.0 Signed-off-by: Dan Benitah <bdanuw@gmail.com>
Documents migration approach, breaking changes, and decision to embrace .NET 10's improved model validation rather than suppressing it. Signed-off-by: Dan Benitah <bdanuw@gmail.com>
- Added ConfigureApiBehaviorOptions to properly handle model validation failures - Added ArgumentNullException and BadHttpRequestException to exception filter - Updated Microsoft.AspNetCore.Mvc.Testing from 6.0.0 to 10.0.0 - Fixes PipeWriter.UnflushedBytes breaking change in .NET 10 All 479 tests now pass (including 108 integration tests that were failing) Signed-off-by: Dan Benitah <bdanuw@gmail.com>
- Updated status to Accepted - Updated migration checklist with completed items - Documented implementation summary and final results Signed-off-by: Dan Benitah <bdanuw@gmail.com>
…tion Signed-off-by: Dan Benitah <bdanuw@gmail.com>
danuw
force-pushed
the
feature/dotnet-10-upgrade
branch
from
2ca814d to
53feb6e
Compare
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.
Pull Request
Issue Number: #657
Summary
One sentence summary of PR
Changes
Checklist
Are there API Changes?
If yes, what are the expected API Changes? Please link to an API-Comparison
workflow with the API Diff.
Is this a breaking change?
If yes, what workflow does this break?
Anything else?
Other comments, collaborators, etc.
This PR Closes #657