EF Core 2.1 Roadmap Update

[steji113]

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]

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

[bricelam]

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]

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]

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

• RevEng: Support Views (RevEng: Support Views #1679)
• Allow for declaring aggregates in the model (Take advantage of ownership to enable aggregate behaviors in model #1985)
• Relational: TPT inheritance mapping pattern (Relational: TPT inheritance mapping pattern #2266)
• Relational: TPC inheritance mapping pattern (Relational: TPC inheritance mapping pattern #3170)
• Turn-key Disconnected Entities Solution (Turn-key Disconnected Entities Solution #5536)
• View types support (Query Types: Model types that do not require identity #9290)

[steji113]

Thanks for the updates!

[divega]

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]

Thanks!

[marchy]

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]

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]

@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]

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]

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]

@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]

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

[ajcvickers]

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