Upgrade to .NET 10 and EF Core 10.0.0#251
Open
benjiro wants to merge 1 commit intoTrackableEntities:masterfrom
Open
Upgrade to .NET 10 and EF Core 10.0.0#251benjiro wants to merge 1 commit intoTrackableEntities:masterfrom
benjiro wants to merge 1 commit intoTrackableEntities:masterfrom
Conversation
- Bump all project TargetFrameworks from net8.0 to net10.0 - Pin Microsoft.EntityFrameworkCore.* packages to 10.0.0 - Update Handlebars.Net to 2.1.6 and JetBrains.Annotations to 2025.2.4 - Update Microsoft.AspNetCore.OpenApi and Web.CodeGeneration.Design to 10.0.0 - Bump package version to 10.0.0 (assembly/file versions updated accordingly) - Fix Check.cs: AbstractionsStrings.CollectionArgumentIsEmpty and ArgumentIsEmpty changed from methods to properties in EF Core 10; replaced with inline interpolated string messages - Update README prerequisites, upgrading steps, and code samples to reflect .NET 10 - Update CodeTemplates PackagePath from lib/net8.0 to lib/net10.0 - TemplatesAssembly remains on netstandard2.1 Signed-off-by: Benjamin Evenson <2031163+benjiro@users.noreply.github.com>
benjiro
force-pushed
the
feature/upgrade-to-dotnet10-efcore10
branch
from
4eb0bb3 to
339aa00
Compare
Author
|
@tonysneed When you get a moment can you review this PR 🙏🏻 |
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
1 participant
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
This PR upgrades the library and all sample/test projects to .NET 10 and pins EF Core to
10.0.0.TargetFrameworkvalues fromnet8.0→net10.0(TemplatesAssembly remains onnetstandard2.1)Microsoft.EntityFrameworkCore.DesignandMicrosoft.EntityFrameworkCore.Relational/SqlServerto10.0.0Handlebars.Netto2.1.6andJetBrains.Annotationsto2025.2.4Microsoft.AspNetCore.OpenApiandMicrosoft.VisualStudio.Web.CodeGeneration.Designto10.0.010.0.0(assembly and file versions updated accordingly)CodeTemplatesNuGet package path fromlib/net8.0→lib/net10.0Resolves #249 #250
Breaking Change Fix
AbstractionsStrings.CollectionArgumentIsEmptyandAbstractionsStrings.ArgumentIsEmptychanged from callable methods to properties in EF Core 10. The calls inInternal/Check.cshave been replaced with equivalent inline interpolated string messages.EF Core Scaffolding Template Compatibility
The EF Core scaffolding generators (
CSharpDbContextGeneratorandCSharpEntityTypeGenerator) are unchanged between v9 and v10 — confirmed by diffing the source files on GitHub. All Handlebars templates (.hbsfiles) and the template data model are fully compatible with EF Core 10 with no modifications required.Test Plan
dotnet buildsucceeds with 0 errors (3 pre-existing connection string warnings in sample projects)dotnet test— succeeds