Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EF Core 2.1 Roadmap Update #9418

Closed
steji113 opened this issue Aug 15, 2017 · 15 comments
Closed

EF Core 2.1 Roadmap Update #9418

steji113 opened this issue Aug 15, 2017 · 15 comments
Assignees
Milestone

Comments

@steji113
Copy link

@steji113 steji113 commented Aug 15, 2017

Roadmap Update

I know EF Core 2.0 was just released, but it might be helpful for contributors and users alike to have an idea of what the roadmap for EF Core 2.1 is looking like. Is this something that can be updated here? Also, it would be an immense help to developers if these feature comparison doc pages could be updated as well here.

Thanks!

@hiyelbaz
Copy link

@hiyelbaz hiyelbaz commented Aug 15, 2017

+1 I think feature comparison should have a higher priority.

@bricelam
Copy link
Member

@bricelam bricelam commented Aug 16, 2017

To see our current ambitions for 2.1, you can always look at the issues in the 2.1.0 milestone with the type-enhancement label.

@MarcoLoetscher
Copy link

@MarcoLoetscher MarcoLoetscher commented Aug 16, 2017

Can you please add the issue number to the following paragraphs:
Critical O/RM features and High priority features according to the paragraph EF Core 2.0 (under development)?
Thanks.

@bricelam
Copy link
Member

@bricelam bricelam commented Aug 16, 2017

Added a few issue numbers. These ones related to some points but didn't cover the whole thing:

  • RevEng: Support Views (#1679)
  • Allow for declaring aggregates in the model (#1985)
  • Relational: TPT inheritance mapping pattern (#2266)
  • Relational: TPC inheritance mapping pattern (#3170)
  • Turn-key Disconnected Entities Solution (#5536)
  • View types support (#9290)
@steji113
Copy link
Author

@steji113 steji113 commented Aug 16, 2017

Thanks for the updates!

@ajcvickers ajcvickers added this to the 2.1.0 milestone Aug 16, 2017
@divega divega added the closed-fixed label Aug 17, 2017
@divega divega closed this Aug 17, 2017
@divega
Copy link

@divega divega commented Aug 17, 2017

I have updated both the roadmap and the feature comparison page.

@bricelam I would like to understand where the list at #9418 (comment) fits 😄

@steji113
Copy link
Author

@steji113 steji113 commented Aug 17, 2017

Thanks!

@marchy
Copy link

@marchy marchy commented Aug 24, 2017

Looking over the roadmap, you have Lazy Loading listed as Critical while TPT as High. I think these should be inversed, since TPT prevents businesses from adopting EF Core while Lazy Loading is simply an optimization that can be done at the code level (ie: either fetch with proper includes upfront or simply query twice). In other words it's not a BLOCKER, while TPT/TPC is.

@weitzhandler
Copy link
Contributor

@weitzhandler weitzhandler commented Aug 24, 2017

I totally second what @marchy said.
TPT is a must in LoB apps, lazy-loading is just another feature (IMHO an evil one).
But, from here I'm not even sure it's gonna be in 2.1. It's not even on the stretch list (any comment @bricelam?), and so is it under the Backlog milestone.

@divega Thanks for updating the roadmap, would be nice if you can point out 2.1 (future) etc. or something similar in the list.

@divega
Copy link

@divega divega commented Aug 25, 2017

@weitzhandler all the empty boxes on the EF Core column would be marked as future. I am reluctant to try to assign items in that table to a more specific milestone because all future plans can change. In the roadmap page we are very explicit about that as a caveat.

@weitzhandler
Copy link
Contributor

@weitzhandler weitzhandler commented Aug 25, 2017

First of all I'm glad to hear you guys have the desire to have the whole table implemented...
And secondly, I'd like to express my appreciation to your intense dedication and responsiveness!
Thank you @divega!

@nefcanto
Copy link

@nefcanto nefcanto commented Dec 25, 2017

Is there a plan for when interceptors come into EF Core? Do they come back at all? I'm about to use reflection as proposed in this link for the sake of interception, but that's really not lightweight.

@ajcvickers
Copy link
Member

@ajcvickers ajcvickers commented Dec 27, 2017

@nefcanto EF Core integrates with DiagnosticSource/DisgnosticListener which can be used for many of the things that EF6 interceptors were used for--see the CoreEventId and RelationalEventId classes for events currently generated.

@nefcanto
Copy link

@nefcanto nefcanto commented Dec 28, 2017

Can you share a link with me on how to do it? I couldn't find one.

@ajcvickers
Copy link
Member

@ajcvickers ajcvickers commented Jan 2, 2018

@nefcanto There is an issue tracking docs for this: dotnet/EntityFramework.Docs#583. Until that is completed, there is an example here: #626 (comment)

@ajcvickers ajcvickers modified the milestones: 2.1.0-preview1, 2.1.0 Nov 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants
You can’t perform that action at this time.