Add Microsoft.EntityFrameworkCore.Design to prevent fallback to 8.x version (#12333)#12335
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThis PR adds explicit ChangesEntityFrameworkCore.Design Package Addition
Estimated Code Review Effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
closes #12333
Summary
Without an explicit reference to
Microsoft.EntityFrameworkCore.Design, the EF Core CLI (dotnet ef) can fall back to resolving an older8.x.xversion of the Design package, which causes compatibility issues in an EF Core 10-powered project.This PR explicitly pins
Microsoft.EntityFrameworkCore.Design(withPrivateAssets="all") in:Directory.Packages.props— central version pin at10.0.7Boilerplate.Server.Api.csproj— unconditional reference (always needs EF migrations)Boilerplate.Server.Web.csproj— conditional reference (same condition asMicrosoft.EntityFrameworkCore.Tools)Summary by CodeRabbit