Skip to content

Document breaking change: EF tools drop .NET Framework support (EF Core 11)#5281

Open
Copilot wants to merge 6 commits intopreview-3from
copilot/document-breaking-change-efcore
Open

Document breaking change: EF tools drop .NET Framework support (EF Core 11)#5281
Copilot wants to merge 6 commits intopreview-3from
copilot/document-breaking-change-efcore

Conversation

Copy link
Contributor

Copilot AI commented Mar 4, 2026

  • Add breaking change entry for .NET Framework support removal (Low impact, clarified error message only)
  • Add separate breaking change entry for Design dependency removal (Low impact)
  • Fix heading levels to match established convention (## for impact sections, ### for titles, #### for subsections)
  • Run markdownlint validation (passes)

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…rojects (#37739)

Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Copilot AI changed the title [WIP] Document breaking change in EF Core pull request 37837 Document breaking change: EF tools drop .NET Framework support (EF Core 11) Mar 4, 2026
…rk framing per review

Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
@AndriySvyryd AndriySvyryd requested a review from Copilot March 4, 2026 03:10
@AndriySvyryd AndriySvyryd marked this pull request as ready for review March 4, 2026 03:10
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the EF Core 11 breaking-changes documentation to capture recent EF tooling-related breaking changes, including clearer behavior around .NET Framework startup projects and the removal of a transitive Microsoft.EntityFrameworkCore.Design dependency from tools packages.

Changes:

  • Adds two new “Low” impact entries to the breaking-changes Summary table.
  • Introduces a new “Low-impact changes” section documenting the two EF tools breaking changes, including rationale and mitigations.

You can also share your feedback on Copilot code review. Take the survey.

AndriySvyryd and others added 2 commits March 3, 2026 19:50
…s.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…s.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: AndriySvyryd <6539701+AndriySvyryd@users.noreply.github.com>
Copy link
Member

@roji roji left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not too sure about the .NET Framework breaking change note - either it's not a breaking change or it may need to be reworded (at least that's how I understood it). But otherwise LGTM.


#### Old behavior

Previously, the EF Core tools (`dotnet-ef` CLI and Package Manager Console tools) did not work with projects targeting .NET Framework, but the error message was unclear.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes it sound like there's no breaking change, and that we just improved the error message? If so do we need an actual breaking change note on this?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was no intentional breaking change, but there is now. I could move it to 9.0 breaking changes if you prefer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants