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

Entity Framework Weekly Status Updates #15403

Open
ajcvickers opened this issue Apr 18, 2019 · 14 comments

Comments

Projects
None yet
1 participant
@ajcvickers
Copy link
Member

commented Apr 18, 2019

This discussion issue contains status updates from the Entity Framework team to provide insight into what we are focused on, progress made, and other interesting highlights from the week.

More Information

Broader information on EF Core planning can be found in the EF Core roadmap.

Use GitHub queries to find full details of

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers ajcvickers added this to the Discussions milestone Apr 18, 2019

@aspnet aspnet locked and limited conversation to collaborators Apr 18, 2019

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Apr 18, 2019

April 18, 2019

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We are preparing to merge the new pipeline in the next couple of weeks.
  • Not everything will be working at that time, but merging will allow us to start gathering feedback.
  • This will likely first ship in EF Core 3.0-preview6.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • We plan to ship a runtime targeting .NET Standard 2.1 with .NET Core 3.0-preview5.
  • Command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status:

  • Most changes here have already been merged.
  • Changes related to the query overhaul will be addressed after the merge of that work.
  • Public API surface for conventions is being work on.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status:

  • Many of the planned breaking changed have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • Work is currently on hold while provider-model and breaking changes are being made

Tracking issue: #12086

Highlights from the last week

Some items of interest from the last week:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers ajcvickers pinned this issue Apr 18, 2019

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Apr 25, 2019

April 25, 2019

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • Progress towards the merge of the new query code is on track for a preview6 release.
  • Not everything will be working at that time, but merging will allow us to start gathering feedback.
  • This will likely first ship in EF Core 3.0-preview6.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • The EF6 runtime has been merged and branched ready for the .NET Core 3.0-preview5 release.
    • For preview5, the ADO.NET provider will need to be registered manually in DbProviderFactories. Details will be in the blog post.
  • Command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status:

  • More internal APIs have been promoted to public this week.
  • Some of the types needed for public conventions are now merged; the remainder is being work on.
  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status:

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • Work is currently on hold while provider-model and breaking changes are being made

Tracking issue: #12086

Latest releases

Nightly builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF Core 3.0 Preview 4 - see our announcement blog post
Current: EF Core 2.2.4
LTS: EF Core 2.1.8

Highlights from the last week

Some items of interest from the last week:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented May 2, 2019

May 2, 2019

Highlights from the last week

Some items of interest from the last week:

A big thank you to all our community contributors!

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • Progress towards the merge of the new query code is on track for a preview6 release. As noted above, the first part has now been merged to master.
  • Not everything will be working at that time, but merging will allow us to start gathering feedback.
  • This will likely first ship in EF Core 3.0-preview6.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • Work continues porting tests to XUnit 2.
  • The EF6 runtime has been merged and branched ready for the .NET Core 3.0-preview5 release.
    • For preview5, the ADO.NET provider will need to be registered manually in DbProviderFactories. Details will be in the blog post.
  • Command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • More internal APIs have been promoted to public this week.
  • Some of the types needed for public conventions are now merged; the remainder is being work on.
  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status: (No change from last week)

  • Work is currently on hold while provider-model and breaking changes are being made

Tracking issue: #12086

Latest releases

Nightly builds: install the latest preview SDK, then use the feeds listed on the repo homepage
Latest preview: EF Core 3.0 Preview 4 - see our announcement blog post
Current: EF Core 2.2.4
LTS: EF Core 2.1.8

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented May 9, 2019

May 9, 2019

Highlights from the last week

Some items of interest from the last week:

A big thank you to @ErikEJ for all his contributions this week!

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have now merged the query overhaul into master ready for EF Core 3.0-preview6.
  • At this time several important features are not fully working. This includes:
    • Many queries involving collection navigation properties
    • Lifting of sub-queries
    • TPH inheritance mapping
    • Queries involving owned types
    • Queries use relational semantics for nulls (as opposed to C# semantics)
  • Also, queries against the in-memory database and Cosmos are not working well. We are currently prioritizing the relational providers over the in-memory provider and Cosmos providers.
  • We are working on fixing the most significant breaks ready for EF Core 3.0-preview6, although some breaks will still remain in that release.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • The Entity Framework 6.3-preview5 package has been pushed to NuGet. See the announcement) for full details.
  • Note that command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.
  • Tests have been ported to XUnit 2. Work is now in progress to get them passing on .NET Core 3.0.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status:

  • More internal APIs have been promoted to public this week. This includes public APIs needed for binding constructors and factory methods of entities as noted above.
  • Some of the types needed for public conventions are now merged; the remainder is being work on.
  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status: (No change from last week)

  • Work is currently on hold while provider-model and breaking changes are being made

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented May 16, 2019

May 16, 2019

Highlights from the last week

Some items of interest from the last week:

Community contributions:

A big thank you to @ErikEJ and @Muppets for their contributions this week!

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Many queries involving collection navigation properties
    • TPH inheritance mapping
    • Queries involving owned types
    • Queries use relational semantics for nulls (as opposed to C# semantics)
  • We are currently working on:
    • Collection navigation property support
    • FromSql
    • C# null semantics
  • Queries against the in-memory database and Cosmos are not working well. We are currently prioritizing the relational providers over the in-memory provider and Cosmos providers.
  • We are working on fixing the most significant breaks ready for EF Core 3.0-preview6, although some breaks will still remain in that release.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • The Entity Framework 6.3-preview5 package has been pushed to NuGet. See the announcement) for full details.
  • Note that command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.
  • Tests have been ported to XUnit 2. Work is now in progress to get them passing on .NET Core 3.0.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status:

  • More work to support public conventions has been merged--see Highlights above for details
  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • Work is currently on hold while provider-model and breaking changes are being made
  • That being said, we have merged some new metadata extensions for Cosmos as part of the public conventions work--see Highlights above for details

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented May 24, 2019

May 23, 2019

Highlights from the last week

Some items of interest from the last week:

  • Further progress has been made on the new query code:
    • Support for C# null semantics has been merged
    • Various other fixes and cleanup to the query code have also been merged
  • We have updated EF Exception classes to use best practices and fix issues with serialization
  • We are continuing with API reviews and other internal tasks

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Many queries involving collection navigation properties
    • TPH inheritance mapping
    • Queries involving owned types
  • We are currently working on:
    • Include and collection navigation property support
    • FromSql
    • SQL Server LongCount support
    • Any/All expression rewriting
    • Entity equality
  • Queries against the in-memory database and Cosmos are not working well. We are currently prioritizing the relational providers over the in-memory provider and Cosmos providers.
  • We are working on fixing the most significant breaks ready for EF Core 3.0-preview6, although some breaks will still remain in that release.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • The Entity Framework 6.3-preview5 package has been pushed to NuGet. See the announcement) for full details.
  • Note that command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.
  • Tests have been ported to XUnit 2. Work is now in progress to get them passing on .NET Core 3.0.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status: (No change from last week)

  • Work is currently on hold while provider-model and breaking changes are being made

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@aspnet aspnet deleted a comment from lajones May 24, 2019

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented May 31, 2019

May 30, 2019

Highlights from the last week

Some items of interest from the last week:

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Many queries involving collection navigation properties
    • Queries involving owned types
  • We are currently working on:
    • Include and collection navigation property support
    • Parameterized FromSql
    • Entity equality
  • Queries against the in-memory database and Cosmos are not working well. We are currently prioritizing the relational providers over the in-memory provider and Cosmos providers.
  • We are working on fixing the most significant breaks ready for EF Core 3.0-preview6, although some breaks will still remain in that release.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • The Entity Framework 6.3-preview5 package has been pushed to NuGet. See the announcement) for full details.
  • Note that command line tooling (for Migrations) and support in the VS Designer is not yet ready to ship.
  • Tests have been ported to XUnit 2. Work is now in progress to get them passing on .NET Core 3.0.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • Work is currently on hold while provider-model and breaking changes are being made
  • Note that the Cosmos provider has not yet been updated to use the new query code and so currently does not work

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jun 6, 2019

June 6, 2019

Highlights from the last week

Some items of interest from the last week:

Community contributions:

A big thank you to @Muppets for all their contributions this week!

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Queries involving owned types
  • We are currently working on:
    • Lots of work on re-enabling functionality in smaller areas
  • Queries against the in-memory database and Cosmos are not working well. We are currently prioritizing the relational providers over the in-memory provider and Cosmos providers.
  • We are working on fixing the most significant breaks ready for EF Core 3.0-preview6, although some breaks will still remain in that release.

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • Tests now run against .NET Core 3.0
  • Work is starting to get the command line tooling for Migrations working in .NET Core
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status: (No change from last week)

  • Work is currently on hold while provider-model and breaking changes are being made
  • Note that the Cosmos provider has not yet been updated to use the new query code and so currently does not work

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jun 13, 2019

June 13, 2019

EF Core 3.0 Preview 6 has shipped!

See the announcement blog post for full details.

In recent months, a lot of our efforts have been focused on a new LINQ implementation for EF Core 3.0. Although the work isn't complete and a lot of the intended functionality hasn't been enabled, before preview 6 we reached a point in which we couldn't make much more progress without integrating the new implementation into the codebase in the main branch.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Temporary limitation: In-memory database and Cosmos DB providers aren't functional in this preview: In the initial phase of the switch to the new implementation, we have prioritized getting our relational providers working. Functionality with in-memory database and Cosmos DB providers is broken, and we recommend you skip preview 6 if you have code that depends on these providers. We expect to gradually restore functionality in subsequent previews.

Other highlights from the last week

Some items of interest from the last week:

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types
    • Collections reference on projections
    • GroupBy operator
    • Query tags
    • Global query filters
  • Queries against the in-memory database and Cosmos are generally not working--see the note at the top of this post

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • Work is continuing to get the command line tooling for Migrations working in .NET Core
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • We have just re-enaged this work; look for updates in the coming weeks.
  • Queries against the in-memory database and Cosmos are generally not working--see the note at the top of this post

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jun 20, 2019

June 20, 2019

EF Core

EF Core 3.0 Preview 6

See the announcement blog post for important details about this preview.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Highlights from the last week

Some items of interest from the last week:

Community contributions:

A big thank you to @Muppets for their contribution this week!

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types
    • Collections reference on projections
    • GroupBy operator
    • Query tags
    • Global query filters
  • Queries against the in-memory database and Cosmos are generally not working--see the preview 6 blog post for details

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Work is continuing to get the command line tooling for Migrations working in .NET Core
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • We are making progress again--see the highlights section for the work completed this week
  • We have now merged preliminary support for queries in Cosmos

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jun 27, 2019

June 27, 2019

EF Core

EF Core 3.0 Preview 6

See the announcement blog post for important details about this preview.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Highlights from the last week

Some items of interest from the last week:

Community contributions

Community contributions to EF Core:

Community contributions to Microsoft.Data.Sqlite:

Community contributions to EF6:

A big thank you to all our great contributors for their contributions this week!

Also, a big call-out to @ericsink for all his great work and collaboration on the SQLitePCL.raw 2.0.0 mentioned above.

Issues remaining for 3.0

This is the burn-down chart we use internally to track progress towards EF Core 3.0. Some observations:

  • It's fairly clear from this chart that we will need to cut some more issues from the 3.0 release. However, keep in mind that many of the remaining issues are small compared to the issues that are already fixed.
  • The gray bar at the top represents all the issues already fixed for 3.0

image

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types
    • Collections referenced on projections
    • GroupBy operator
    • Query tags
    • Global query filters
  • Queries against the in-memory database and Cosmos are generally not working--see the preview 6 blog post for details

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Work is continuing to get the command line tooling for Migrations working in .NET Core
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • We are making progress again--see the highlights section for the work completed this week
  • We have now merged preliminary support for queries in Cosmos

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jul 5, 2019

July 5, 2019

EF Core

EF Core 3.0 Preview 6

See the announcement blog post for important details about this preview.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Highlights from the last week

Some items of interest from the last week:

Community contributions

Community contributions to EF Core:

Community contributions to EF6:

A big thank you to all our great contributors for their contributions this week!

Also, a big call-out to all the folks from the NTS project including @airbreather and @FObermaier for all their great work and collaboration on NetTopologySuite 2.0 preview release mentioned above.

Issues remaining for 3.0

This is the burn-down chart we use internally to track progress towards EF Core 3.0. Some observations:

  • EF Core 3.0 is coming in hot; last week we postponed all issues that we did not absolutely need in order to ship the 3.0 release. Most of these were very painful cuts, but this was necessary to stay on track for shipping.
  • The gray bar at the top represents all the issues already fixed for 3.0

image

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types
    • Global query filters
  • Queries against the in-memory database are generally not working--see the preview 6 blog post for details

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • Work is continuing to get the command line tooling for Migrations working in .NET Core
    • Updates to the package install experience for .NET Core and the new project system have been made
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • We are making progress again--see the highlights section for the work completed this week
  • More Cosmos query support has now been added

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jul 11, 2019

July 11, 2019

EF Core

EF Core 3.0 Preview 6

See the announcement blog post for important details about this preview.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Highlights from the last week

Some items of interest from the last week:

Community contributions

A special call-out this week to @Wraith2 who contributed a feature to Microsoft.Data.SqlClient that unblocked important spatial scenarios for EF Core. Many thanks!

Issues remaining for 3.0

This is the burn-down chart we use internally to track progress towards EF Core 3.0. Some observations:

  • Burn-down is on-track for shipping after the recent painful cuts
  • The gray bar at the top represents all the issues already fixed for 3.0

image

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types
    • Global query filters
    • Queries against the in-memory provider
    • Explicitly compiled queries

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Work is continuing to get the command line tooling for Migrations working in .NET Core
    • Updates to the package install experience for .NET Core and the new project system have been made
  • Support in the VS Designer is not yet ready to ship.

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • We are making progress again, this week focusing on some big changes to support more queries

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

commented Jul 18, 2019

July 18, 2019

EF Core

EF Core 3.0 Preview 6

See the announcement blog post for important details about this preview.

IMPORTANT: Although as always, we want to encourage you to experiment with our preview bits in a controlled environment and to provide feedback, preview 6 has significant limitations in the LINQ implementation that we expect to affect any application that performs all but the most trivial queries. Given this, we want to explicitly recommend you against trying to update any applications you have in production to this preview.

Highlights from the last week

Some items of interest from the last week:

Community contributions

Community contributions to EF Core:

A big thank you to @ralmsdeveloper for their contribution this week!

Issues remaining for 3.0

This is the burn-down chart we use internally to track progress towards EF Core 3.0. Some observations:

  • Burn-down slowed slightly this week due to API reviews and other internal work
  • The gray bar at the top represents all the issues already fixed for 3.0

image

Major areas

While engineers frequently work on multiple things in parallel, these are the high-level areas that we are focusing on for the EF Core 3.0 release.

Query pipeline overhaul

What: The way LINQ queries are translated is getting a major overhaul for EF Core 3.0. Part of this involves removal of automatic client evaluation, except in the final projection.

Status:

  • We have merged more progress on the new query pipeline--see Highlights above for details.
  • At this time several important features are not fully working. This includes:
    • Owned types - owned references now work; owned collections coming soon
    • Global query filters
    • Queries against the in-memory provider is currently in progress
    • Explicitly compiled queries - this should be complete in the coming days

Tracking issue: #12795

Porting EF6 to .NET Core

What: Support EF6 on .NET Core.

Status:

  • Migrations commands are now working for .NET Core projects in the Visual Studio Package Manager Console!
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: aspnet/EntityFramework6#271

Provider model updates

What: We are promoting some internal types and concepts to public so that they can be consumed safely from database providers.

Status: (No change from last week)

  • Changes related to the query overhaul will be addressed after the merge of that work.

Tracking issue: #15405

Breaking changes

What: We are making a number of breaking changes for EF Core 3.0 to improve the experience and functionality of EF Core in various important ways.

Status: (No change from last week)

  • Many of the planned breaking changes have now been merged
  • Remaining planned breaking changes are mostly around the query overhaul and provider model updates
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider

What: We are continuing work on the EF Core database provider for Azure Cosmos.

Status:

  • Good progress is being made on queries for owned entities

Tracking issue: #12086

Latest releases

EF Core:

EF6:

More Information

See the top of this issue for links to more information.

Comments are disabled on this issue to reduce noise. Please use the related discussion issue for any comments on these status updates.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.