Fix NullReferenceException in dbcontext optimize with cross-version compatibility #37547
+4
−1
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.
The
dotnet ef dbcontext optimizecommand throws a NullReferenceException when using dotnet-ef tools ≥9.0 with EF Core 8.0 projects, despite successfully generating the compiled model.Root Cause
EF Core 8.0's
DbContextOperations.Optimizereturnsvoid, while 9.0+ returnsIReadOnlyList<string>. When the 9.0+ tool invokes the 8.0 runtime via reflection, it receivesnulland attempts to enumerate it inReportResults.Changes
ReportResultsinDbContextOptimizeCommand.ExecuteThis aligns with the tool's cross-version support pattern established in #37201.
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.