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 (2019) #15403

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

Entity Framework Weekly Status Updates (2019) #15403

ajcvickers opened this issue Apr 18, 2019 · 30 comments
Milestone

Comments

@ajcvickers
Copy link
Member

@ajcvickers ajcvickers commented Apr 18, 2019

Weekly status updates for 2020 can be found at: #19549

Expand to see additional information from the end of 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

Please note that there is never a guarantee that an issue will be fixed in its assigned release. Re-evaluation of the plan throughout the release cycle sometimes results in issues being pushed out to a later release.

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
@dotnet dotnet locked and limited conversation to collaborators Apr 18, 2019
@ajcvickers

This comment has been minimized.

Copy link
Member Author

@ajcvickers ajcvickers commented Apr 18, 2019

April 18, 2019

Expand to see status from 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 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: dotnet/ef6#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

@ajcvickers ajcvickers commented Apr 25, 2019

April 25, 2019

Expand to see status from 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:

  • 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: dotnet/ef6#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

@ajcvickers ajcvickers commented May 2, 2019

May 2, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented May 9, 2019

May 9, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented May 16, 2019

May 16, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented May 24, 2019

May 23, 2019

Expand to see status from this week...

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: dotnet/ef6#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.

@dotnet dotnet deleted a comment from lajones May 24, 2019
@ajcvickers

This comment has been minimized.

Copy link
Member Author

@ajcvickers ajcvickers commented May 31, 2019

May 30, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jun 6, 2019

June 6, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jun 13, 2019

June 13, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jun 20, 2019

June 20, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jun 27, 2019

June 27, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jul 5, 2019

July 5, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jul 11, 2019

July 11, 2019

Expand to see status from this week...

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: dotnet/ef6#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

@ajcvickers ajcvickers commented Jul 18, 2019

July 18, 2019

Expand to see status from this week...

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: dotnet/ef6#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.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

@ajcvickers ajcvickers commented Jul 25, 2019

July 25, 2019

Expand to see status from this week...

EF Core 3.0 Preview 7 and EF6.3 Preview 7 have shipped!

See the announcement blog post for full details.

We encourage you to install these previews to try the new features, and to validate that all the functionality required by your applications is available and works correctly. As always, we hope you’ll report any issues you find on GitHub.

Nightly builds

The state of EF Core 3.0 is evolving rapidly--at the time of writing, 45 issues have been fixed since we branched for preview 7. Therefore, we recommend switching to nightly builds if you are running into issues with preview 7.

Highlights from the last week

Some items of interest from the last week:

Community contributions

Community contributions to EF Core:

In his role as one of the maintainers of the Npgsql database provider, @roji has updated the provider to work with preview 7 of EF Core.

This week, @ErikEJ contributed:

A big thank you to @ErikEJ for all his contributions this week and over the years!

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 picking up again now API reviews have finished
  • 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, but are coming soon. This includes:
    • Owned collections
    • Global query filters
    • Better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status:

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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

Status:

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • 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:

  • As referenced above, collections embedded in documents are now supported

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

@ajcvickers ajcvickers commented Aug 1, 2019

August 1, 2019

Expand to see status from this week...

EF Core 3.0 Preview 7 and EF6.3 Preview 7 have shipped!

See the announcement blog post for full details.

We encourage you to install these previews to try the new features, and to validate that all the functionality required by your applications is available and works correctly. As always, we hope you’ll report any issues you find on GitHub.

Nightly builds

The state of EF Core 3.0 is evolving rapidly--at the time of writing, 75 issues have been fixed since we branched for preview 7. Therefore, we recommend switching to nightly builds if you are running into issues with preview 7.

Highlights from the last week

EF Core pull requests from the last week:

EF6 pull requests from the last 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:

  • The gray bar at the top represents all the issues already fixed for 3.0
  • Current counts and trends:
    • Open for 3.0: 72
    • Burn rate (July): 23/week (trending up)
    • Incoming that land in 3.0: (July): 10/week (flat)

image

Some additional stats

The team prepared some additional statistics for a management review this week. We are sharing them here in case others are interested.

There were 220 issues opened against EF Core in July. This chart shows the breakdown of how those issues were resolved:

image

We have fixed a total of 249 issues in preview 6, 7, 8, and so far for preview 9. 72 issues remain to be fixed in the 3.0 release.

image

TechEmpower perf update

We switched perf infrastructure over to use the latest Npgsql provider and the new query pipeline. We haven't done performance optimization work yet, so it it pleasing to see no regressions for EF Core in "Fortunes" and "Data Updates", and only small regressions in "Single Query" and "Multi Query".

image

image

image

image

NuGet Trends

We have been enjoying playing with the NuGet Trends site; here are a couple of interesting comparisons. Clearly EF Core is trending in the right direction, and it's great to see Dapper continuing to do well, and nHibernate continuing to be a great solution for those that prefer it.

image

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, but are coming soon. This includes:
    • Owned collections
    • Global query filters
    • Better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • 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 moving along nicely for an RTM release with 3.0--see highlights section 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

@ajcvickers ajcvickers commented Aug 8, 2019

August 8, 2019

Expand to see status from this week...

EF Core 3.0 Preview 7 and EF6.3 Preview 7 are on NuGet

See the announcement blog post for full details.

We encourage you to install these previews to try the new features, and to validate that all the functionality required by your applications is available and works correctly. As always, we hope you’ll report any issues you find on GitHub.

Nightly builds

The state of EF Core 3.0 is evolving rapidly--at the time of writing, 107 issues have been fixed since we branched for preview 7. Therefore, we recommend switching to nightly builds if you are running into issues with preview 7.

Highlights from the last week

EF Core pull requests from the last week:

EF6 pull requests from the last week:

Community contributions

Community contributions to EF Core:

Many thanks to @chiasottis for their contribution.

Issues remaining for 3.0

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

  • 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, but are coming soon. This includes:
    • Global query filters
    • Better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider (Done)

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

Status:

  • All the major features we plan to ship in 3.0 are now done.

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

@ajcvickers ajcvickers commented Aug 15, 2019

August 15, 2019

Expand to see status from this week...

EF Core 3.0 Preview 8 and EF6.3 Preview 8 have shipped!

The EF Core 3.0 preview 8 package and EF 6.3 preview 8 package are now available for download from NuGet.

See the announcement blog post for full details.

Please install these previews to validate that all the functionality required by your applications is available and works correctly.

Please report any issues you find as soon as possible to either the EF Core issue tracker or the EF 6 issue tracker on GitHub.

At this point, we are especially interested in hearing about all issues blocking you from upgrading to the new releases, but please also try new functionality and provide general feedback.

Daily builds

The state of EF Core 3.0 is evolving rapidly--at the time of writing, 80 issues have been fixed since we branched for preview 8! Therefore, we recommend switching to daily builds if you are running into issues with preview 8. Note that the daily builds require the .NET Core preview 8 SDK to be installed.

Highlights from the last week

EF Core pull requests from the last week:

EF6 pull requests from the last week:

Community contributions

Community contributions to EF Core:

Community contributions to EF6:

Many thanks to all our contributors this week for their hard work!

Issues remaining for 3.0

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

  • 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, but are coming soon. This includes:
    • Better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider (Done)

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

Status: (No change from last week)

  • All the major features we plan to ship in 3.0 are now done.

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

@ajcvickers ajcvickers commented Aug 22, 2019

August 22, 2019

Expand to see status from this week...

EF Core 3.0 and EF6.3 have branched for preview 9!

Preview 9 won't be on NuGet for a while yet, but please don't wait! Instead, get your feedback in early by using the daily builds which include 117 issues fixed since preview 8! Note that the daily builds require the .NET Core preview 8 SDK to be installed.

Please report any issues you find as soon as possible to either the EF Core issue tracker or the EF 6 issue tracker on GitHub.

At this point, we are especially interested in hearing about all issues blocking you from upgrading to 3.0, but please also try new functionality and provide general feedback.

See the preview 8 announcement blog post for more general information as well as information specific to preview 8.

Highlights from the last week

EF Core pull requests from the last week:

EF6 pull requests from the last week:

Community contributions

Community contributions to EF Core:

Many thanks to all our contributors this week for their hard work!

Issues remaining for 3.0

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

  • The gray bar at the top represents all the issues already fixed for 3.0 - we are now at 517 issues fixed!
  • We have two issues still being worked on for 3.0:
  • We are not planning anything else for 3.0, but high-priority fixes may still get made with director-level approval

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:

  • Currently the only remaining work planned for 3.0 is better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider (Done)

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

Status: (No change from last week)

  • All the major features we plan to ship in 3.0 are now done.

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

@ajcvickers ajcvickers commented Aug 29, 2019

August 29, 2019

Expand to see status from this week...

Try EF Core 3.0 and EF6.3 now!

Preview 9 won't be on NuGet for a while yet, but please don't wait! Instead, get your feedback in early by using the daily builds which include 134 issues fixed since preview 8! Note that the daily builds require the .NET Core preview 8 SDK to be installed.

The current daily builds are close to what we will ship for 3.0, other than a few areas in the in-memory provider. Please try it now while there is still time to fix any serious issues found.

Report any issues you find as soon as possible to either the EF Core issue tracker or the EF 6 issue tracker on GitHub.

See the preview 8 announcement blog post for more general information as well as information specific to preview 8.

Highlights from the last week

EF Core pull requests from the last week:

Community contributions

Community contributions to EF Core:

Many thanks to @skalpin for their contribution!

Issues remaining for 3.0

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

  • The gray bar at the top represents all the issues already fixed for 3.0 - we are now at 536 issues fixed!
  • We have one issue still being worked on for 3.0:
  • We are not planning anything else for 3.0, but high-priority fixes may still make it to the release with director-level approval

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:

  • Currently the only remaining work planned for 3.0 is better support for queries against the in-memory provider

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider (Done)

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

Status: (No change from last week)

  • All the major features we plan to ship in 3.0 are now done.

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

@ajcvickers ajcvickers commented Sep 5, 2019

September 5, 2019

Expand to see status from this week...

EF Core 3.0 and EF6.3 preview 9 released!

These are the last planned previews before we release the final versions later this month. We have almost completely stopped making changes to the product code, but we are still actively monitoring feedback for any important bugs that may be reported. So please install the previews to validate that all the functionality required by your applications is available and works correctly, and report any issues you find to either the EF Core issue tracker or the EF 6 issue tracker on GitHub.

Even if we may not be able to fix many more issues in EF Core 3.0 at this point, we’ll consider important bugs and regressions for the upcoming 3.1 release.

See the preview 9 announcement blog post for more general information as well as information specific to preview 9.

Consider installing daily builds

In Preview 9 the functionality of the in-memory provider is still very limited, but this is already fixed in our daily builds. In fact, we have already fixed more than 20 issues that aren’t included in Preview 9, and we may still fix a few more before RTM.

Detailed instructions to install daily builds, including the necessary NuGet feeds, can be found in the How to get daily builds of ASP.NET Core article.

What are we doing now?

Now that 3.0 is wrapping up, the EF team is transitioning to working on:

  • Bug fixes for 3.1.
    • 3.1 will be a LTS (Long Term Support) release, so we're stabilizing and fixing bugs for this release
    • 3.1 will not have new features without .NET Director-level approval
  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Pull requests from the last week

EF Core

Documentation

Community contributions

Community contributions to documentation:

Many thanks to @ronnelsantiago for their contribution!

Issues remaining for 3.0

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

  • The gray bar at the top represents all the issues already fixed for 3.0 - we are now at 551 issues fixed!
  • We are not planning anything else for 3.0, but high-priority fixes may still make it to the release with director-level approval

(You may be wondering why the count of issues fixed in 3.0 keeps going up even though we are done with 3.0. This is because we have a lot of issues that we think are fixed for 3.0, but which we haven't verified as fixed. Once we have verified that an issue has been fixed in 3.0, then we move that closed issue into the 3.0 milestone to reflect this.)

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 (Done)

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 done with planned work for 3.0. Additional bug fixes and stabilization are happening for the 3.1 LTS release.

Tracking issue: #12795

Porting EF6 to .NET Core (Done)

What: Support EF6 on .NET Core.

Status: (No change from last week)

  • Major feature work for the EF6.3 release is now complete.
  • Support in the VS Designer will now ship sometime after the runtime release

Tracking issue: dotnet/ef6#271

Provider model updates (Done)

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)

  • API reviews have been completed and the surface area for providers is now locked down. There may still be some small tweaks before release based on feedback from external providers.

Tracking issue: #15405

Breaking changes (Done)

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)

  • We have now completed all the significant breaking changes we plan to make for the 3.0 release. There may still be some small tweaks before release based on feedback.
  • Breaking changes, including mitigations, are documented in the EF Core breaking changes doc.

Tracking issue: #15407

Cosmos database provider (Done)

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

Status: (No change from last week)

  • All the major features we plan to ship in 3.0 are now done.

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.

@divega

This comment has been minimized.

Copy link

@divega divega commented Sep 20, 2019

September 19, 2019

Expand to see status from this week...

EF Core 3.0 and EF6.3 GA around the corner! Team focused on documentation updates and EF Core 3.1 improvements

We previously said that preview 9 would be your last chance to test EF Core 3.0 and EF 6.3 before general availability.

It turns out we made enough improvements to our libraries and across the whole of .NET Core 3.0 to justify publishing a release candidate build. Hence the packages for EF Core 3.0 RC1 and EF 6.3 RC1 are now available.

These are the last previews (this time for real! 😄) before we release the final versions on September 23 during .NET Conf.

We hope you can tune in for the talk Entity Framework Core 3.0 and beyond, at 3:00 PM PDT (22:00 UTC), with @divega and @smitpatel!

Consider installing daily builds

Even the RC1 builds come form branches that were frozen a couple of weeks ago, so there are at least a few additional bug fixes in our daily builds.

At this point we have completely stopped making changes to the product code in the release branches, an unless something really critical comes up, the current state of our daily builds is what we will release.

Anyway, if you find a bug now, please report it as soon as possible in either the EF Core issue tracker or the EF 6 issue tracker on GitHub. Even if we won't be able to fix any more issues in EF Core 3.0, we’ll consider them for 3.1.

Detailed instructions to install daily builds, including the necessary NuGet feeds, can be found in the How to get daily builds of ASP.NET Core article.

What are we doing now?

Now that 3.0 is wrapping up, our team is focused on making sure the documentation is ready for the imminent release, coding improvements to be included in EF Core 3.1 (to be released later this year), and paying technical debt.

EF Core 3.1

EF Core 3.1 will be a LTS (Long Term Support) release, so the focus is on stabilizing and fixing bugs rather than adding features. In fact, including new features in 3.1 requires .NET team's director-level approval.

The full set of issues fixed in 3.1 can seen by querying our issue tracker. Here are some worth mentioning:

  • Fixes and improvements for issues found in the last minute for Cosmos DB provider
  • Fixes and improvements for issues found in the last minute in the new LINQ pipeline
  • Lots of regressions tests added for issues verified as fixed in 3.0
  • Test stability improvements (investigating and fixing remaining flaky tests)
  • Code cleanup.

Documentation updates

There are several kinds of updates we are making to our documentation:

  1. New articles that cover new features in 3.0, like the Cosmos DB provider docs
  2. Update existing articles to reflect the actual behavior and API changes in the new releases, like the new Keyless Entity Types document that replaces Query Types and the updated EF 6.3 release notes
  3. Overhaul of the getting started docs to make them more approachable and easier to follow (work in progress).
  4. General re-organization of docs and additional cross-references to make things easier to find
  5. Adding more details and clarifications to existing docs
  6. Updating the samples and adding more examples

EF Core “5.0”

We took another community PR for the next major version of EF Core last week. Thank you @SARAVANA1501 for your contribution.

@ajcvickers

This comment has been minimized.

Copy link
Member Author

@ajcvickers ajcvickers commented Oct 17, 2019

October 17, 2019

Expand to see status from this week...

After a few weeks break while I have been away, EF weekly updates are now back!

EF Core 3.1

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
  • We have fixed 83 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 1 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds. For example, the daily builds of 3.1 contain fixes for 34 issues not in the preview 1 release.
  • Current: EF Core 3.0.0
  • LTS: EF Core 2.1.14

What are we doing now?

We are currently spending most of our time fixing bugs for the 3.1 release--see above.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.

Pull requests from the last week

EF Core

Documentation

Community contributions

Many thanks to both for these contributions!

Issues remaining for 3.1

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

  • The gray bar at the top represents all the issues already fixed for 3.1 - we are at 83 issues fixed

image

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

@ajcvickers ajcvickers commented Oct 24, 2019

October 24, 2019

Expand to see status from this week...

EF Core 3.1

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
  • We have fixed 110 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 1 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds. For example, the daily builds of 3.1 contain fixes for 61 issues not in the preview 1 release.
  • Current: EF Core 3.0.0
  • LTS: EF Core 2.1.11

What are we doing now?

We are currently spending most of our time fixing bugs for the 3.1 release--see above.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.

Pull requests from the last week

EF Core

EF6

Microsoft.Data.Sqlite:

Documentation

Community contributions

Many thanks for your contributions!

Issues remaining for 3.1

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

  • The gray bar at the top represents all the issues already fixed for 3.1 - we are at 110 issues fixed

image

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

@ajcvickers ajcvickers commented Oct 31, 2019

October 31, 2019

Expand to see status from this week...

EF Core 3.1

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
  • We have fixed 129 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release. However, note that the builds are currently a few days old as we work through infrastructure issues.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 1 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds. For example, the daily builds of 3.1 contain fixes for 61 issues not in the preview 1 release.
  • Current: EF Core 3.0.0
  • LTS: EF Core 2.1.11

What are we doing now?

We are currently spending most of our time fixing bugs for the 3.1 release--see above.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.

Pull requests from the last week

EF Core

EF6

Microsoft.Data.Sqlite:

Documentation

Community contributions

Many thanks for your contributions!

Issues remaining for 3.1

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

  • The gray bar at the top represents all the issues already fixed for 3.1 - we are at 129 issues fixed

image

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

@ajcvickers ajcvickers commented Nov 7, 2019

November 7, 2019

Expand to see status from this week...

EF Core 3.1

EF Core 3.1 Preview 2 is on NuGet! However, we still recommend using the daily builds--see below.

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
  • We have fixed 140 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 2 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds. For example, the daily builds of 3.1 contain fixes for 36 issues not in the preview 2 release.
  • Current: EF Core 3.0.0
  • LTS: EF Core 2.1.11

What are we doing now?

We are currently spending most of our time fixing bugs for the 3.1 release--see above.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Planning for the "5.0" release (i.e. the one after 3.1) will start in the coming weeks.

Pull requests from the last week

This week we have merged 12 pull requests from community contributors! Way to go, community! Thanks so much!

Community contributions

EF Core

Issues remaining for 3.1

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

  • The gray bar at the top represents all the issues already fixed for 3.1 - we are at 140 issues fixed

image

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

@ajcvickers ajcvickers commented Nov 14, 2019

November 14, 2019

Expand to see status from this week...

EF Core 3.1

EF Core 3.1 Preview 3 is on NuGet! This is the last preview before GA/RTM and contains almost everything we plan to ship in 3.1. Please try it now!

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long term support (LTS)
  • We have fixed 145 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 3 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub, and so are usually not as good an option as the daily builds.
  • Current: EF Core 3.0.0
  • LTS: EF Core 2.1.11

What are we doing now?

The 3.1 release is now locked down; we don't expect to put any more changes into 3.1.

Planning for the "5.0" release (i.e. the one after 3.1) has started! We will share more in the coming weeks.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Re-organization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Pull requests from the last week

Community contributions

Many thanks to @vanillajonathan and @jtheisen!

EF Core

Issues remaining for 3.1

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

  • As stated above, we don't have any more changes planned for 3.1.
  • The gray bar at the top represents all the issues already fixed for 3.1 - we are at 145 issues fixed

image

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

@ajcvickers ajcvickers commented Nov 21, 2019

November 21, 2019

Expand to see status from this week...

EF Core 3.1

EF Core 3.1 Preview 3 is on NuGet! This is the last preview before GA/RTM and contains almost everything we plan to ship in 3.1. Please try it now!

What you need to know about EF Core 3.1:

  • The release cycle is short--EF Core 3.1 is scheduled for release on December 3.
  • The goal of this release is to stabilize 3.0 and fix bugs to prepare 3.1 for long-term support (LTS)
  • We have fixed 150 issues so far
  • EF Core 3.1 contains no new significant features

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Currently we have daily builds for 3.1 and for "5.0". Most work is currently going into the 3.1 builds.
  • EF Core 3.1 preview 3 is available now on NuGet.
    • Preview releases on NuGet are a reasonable way to help find issues and provide feedback. However, keep in mind that these releases tend to lag a couple weeks from what is happening on GitHub. This means daily builds are often a better option.
  • Current: EF Core 3.0.1
  • LTS: EF Core 2.1.14

What are we doing now?

The 3.1 release is now locked down; we don't expect to put any more changes into 3.1.

Critical bugs in 3.1 are now being considered for patch releases.

Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We will have something to share soon.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 release
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Reorganization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements

Pull requests from the last week

Community contributions

Many thanks to all our contributors this week!

EF Core

Issues remaining for 3.1

The 3.1 release is now closed down. The burn-down will return for 5.0 once the plan is ready.

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

@ajcvickers ajcvickers commented Dec 5, 2019

December 5, 2019

Expand to see status from this week...

EF Core 3.1

The GA/RTM release of EF Core 3.1 is out and available on NuGet now!

What's new in 3.1?

The primary goal of EF Core 3.1 is to polish the features and scenarios we delivered in EF Core 3.0. EF Core 3.1 will be a long term support (LTS) release, supported for at least 3 years. To this end we have fixed over 150 issues for the 3.1 release, but there are no major new features to announce.

Support for .NET Standard 2.0

EF Core 3.1 reintroduces support for .NET Standard 2.0, rather than requiring .NET Standard 2.1 as was the case for EF Core 3.0. This means EF Core 3.1 will run on .NET Framework versions supported by the standard.

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Daily builds now contain work scheduled for release in EF Core 5.0.
  • Current: EF Core 3.1.0
  • LTS: EF Core 3.1.0

EF 6.4

The GA/RTM release of EF 6.4 is also out and available on NuGet now. Similar to EF Core, the primary goal of EF 6.4 is to polish the features and scenarios we delivered in EF 6.3. To this end we have fixed important issues found in EF 6.3 to create a more stable release.

What are we doing now?

Critical bugs in 3.1 are now being considered for patch releases. The first patch release is tentatively scheduled for January.

Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We will have something to share soon.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 and 3.1 releases
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Reorganization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements
  • Holiday spirit and recovering from the intense 3.0/3.1 release!

New features in EF Core 5.0

As stated above, planning of 5.0 major features is ongoing, but in addition to bug fixes we have already merged a few small features/enhancements.

Simple Logging

This feature is the moral equivalent of Database.Log in EF6. That is, it provides a simple way to get logs from EF Core without the need to configure any kind of external logging framework.

EF Core replaces Database.Log with a LogTo method called on DbContextOptionsBuilder in either AddDbContext or OnConfiguring. For example:

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
    => optionsBuilder.LogTo(Console.WriteLine);

Overloads exist to:

  • Set the minimum log level
    • Example: .LogTo(Console.WriteLine, LogLevel.Information)
  • Filter for only specific events:
    • Example: .LogTo(Console.WriteLine, new[] {CoreEventId.ContextInitialized, RelationalEventId.CommandExecuted})
  • Filter for all events in specific categories:
    • Example: .LogTo(Console.WriteLine, new[] {DbLoggerCategory.Database.Name}, LogLevel.Information)
  • Use a custom filter over event and level:
    • Example: .LogTo(Console.WriteLine, (id, level) => id == RelationalEventId.CommandExecuting)

Output format can be minimally configured (API is in flux) but the default output looks something like:

warn: 12/5/2019 09:57:47.574 CoreEventId.SensitiveDataLoggingEnabledWarning[10400] (Microsoft.EntityFrameworkCore.Infrastructure)
      Sensitive data logging is enabled. Log entries and exception messages may include sensitive application data, this mode should only be enabled during development.
dbug: 12/5/2019 09:57:47.581 CoreEventId.ShadowPropertyCreated[10600] (Microsoft.EntityFrameworkCore.Model.Validation)
      The property 'BlogId' on entity type 'Post' was created in shadow state because there are no eligible CLR members with a matching name.
info: 12/5/2019 09:57:47.618 CoreEventId.ContextInitialized[10403] (Microsoft.EntityFrameworkCore.Infrastructure)
      Entity Framework Core 5.0.0-dev initialized 'BloggingContext' using provider 'Microsoft.EntityFrameworkCore.SqlServer' with options: SensitiveDataLoggingEnabled
dbug: 12/5/2019 09:57:47.644 CoreEventId.ValueGenerated[10808] (Microsoft.EntityFrameworkCore.ChangeTracking)
      'BloggingContext' generated temporary value '-2147482647' for the 'Id' property of new 'Blog' entity.
...

Translation of Contains on byte arrays

Queries using Contains on byte[] properties are now translated to SQL. For example:

var blogs = context.Blogs.Where(e => e.Picture.Contains((byte)127)).ToList();

Translates to the following on SQL Server:

info: 12/5/2019 11:42:42.022 RelationalEventId.CommandExecuted[20101] (Microsoft.EntityFrameworkCore.Database.Command)
      Executed DbCommand (1ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
      SELECT [b].[Id], [b].[Picture], [b].[Title]
      FROM [Blogs] AS [b]
      WHERE CHARINDEX(0x7F, [b].[Picture]) > 0

Pull requests from the last two weeks

Community contributions

Many thanks to all our contributors!

EF Core

Issues remaining for 5.0

The burn-down will return for 5.0 once the plan is ready.

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

@ajcvickers ajcvickers commented Dec 12, 2019

December 12, 2019

Expand to see status from this week...

EF Core 3.1

The GA/RTM release of EF Core 3.1 is out and available on NuGet now!

Builds to use

  • The daily builds are the most up-to-date available.
    • Using the daily builds is a great way to find issues and provide feedback as early as possible. The sooner we get such feedback, the more likely it will be actionable before the next official release.
    • We work hard to keep the daily builds in good shape by running over 50,000 tests per TFM for each build.
    • Daily builds now contain work scheduled for release in EF Core 5.0.
  • Current: EF Core 3.1.0
  • LTS: EF Core 3.1.0

What are we doing now?

Critical bugs in 3.1 are now being considered for patch releases. The first patch release is tentatively scheduled for January.

Planning for the "5.0" release (i.e. the one after 3.1) has started and we are making good progress. We need to sync with the .NET directors before we can share publicly.

In addition, we are working on:

  • Technical debt
    • Code cleanup, additional testing, test reliability, etc.
  • Documentation
    • Updating docs to be cover changes in the 3.0 and 3.1 releases
    • An overhaul of the getting started docs to make them more approachable/easier to follow
    • Reorganization of docs to make things easier to find and to add cross-references
    • Adding more details and clarifications to existing docs
    • Updating the samples and adding more examples
  • Planning and process improvements
  • Holiday spirit and recovering from the intense 3.0/3.1 release!

New features in EF Core 5.0

As stated above, planning of 5.0 major features is ongoing, but in addition to bug fixes we have already merged a few small features/enhancements.

Debug views

Debug views are an easy way to look at the internals of EF Core when debugging issues. A debug view for the Model was implemented some time ago. For EF Core 5.0, we have made the model view easier to read and added a new debug view for tracked entities in the state manager.

Model debug view

Drill down into the Model property of the DbContext in your debugger of choice and expand the DebugView property.

image

The LongView is the model view we have had for some time. The ShortView is new and doesn't include model annotations, which make it much easier to read. For example, here is one of our test models:

Model: 
  EntityType: Chassis
    Properties: 
      TeamId (int) Required PK FK AfterSave:Throw
      Name (string)
      Version (no field, byte[]) Shadow Concurrency BeforeSave:Ignore AfterSave:Ignore ValueGenerated.OnAddOrUpdate
    Navigations: 
      Team (_team, Team) ToPrincipal Team Inverse: Chassis PropertyAccessMode.Field
    Keys: 
      TeamId PK
    Foreign keys: 
      Chassis {'TeamId'} -> Team {'Id'} Unique ToDependent: Chassis ToPrincipal: Team
  EntityType: Driver
    Properties: 
      Id (int) Required PK AfterSave:Throw ValueGenerated.OnAdd
      CarNumber (Nullable<int>)
      Championships (int) Required
      Discriminator (no field, string) Shadow Required
      FastestLaps (int) Required
      Name (string)
      Podiums (int) Required
      Poles (int) Required
      Races (int) Required
      TeamId (int) Required FK Index
      Version (no field, byte[]) Shadow Concurrency BeforeSave:Ignore AfterSave:Ignore ValueGenerated.OnAddOrUpdate
      Wins (int) Required
    Navigations: 
      Team (_team, Team) ToPrincipal Team Inverse: Drivers PropertyAccessMode.Field
    Keys: 
      Id PK
    Foreign keys: 
      Driver {'TeamId'} -> Team {'Id'} ToDependent: Drivers ToPrincipal: Team
    Indexes: 
      TeamId
  EntityType: Engine
    Properties: 
      Id (int) Required PK AfterSave:Throw ValueGenerated.OnAdd
      EngineSupplierId (int) Required FK Index Concurrency
      Name (string) Concurrency
    Navigations: 
      EngineSupplier (_engineSupplier, EngineSupplier) ToPrincipal EngineSupplier Inverse: Engines PropertyAccessMode.Field
      Gearboxes (_gearboxes, ICollection<Gearbox>) Collection ToDependent Gearbox PropertyAccessMode.Field
      StorageLocation (Location) ToDependent Location PropertyAccessMode.Field
      Teams (_teams, ICollection<Team>) Collection ToDependent Team Inverse: Engine PropertyAccessMode.Field
    Keys: 
      Id PK
    Foreign keys: 
      Engine {'EngineSupplierId'} -> EngineSupplier {'Id'} ToDependent: Engines ToPrincipal: EngineSupplier
    Indexes: 
      EngineSupplierId
  EntityType: EngineSupplier
    Properties: 
      Id (int) Required PK AfterSave:Throw ValueGenerated.OnAdd
      Name (string)
    Navigations: 
      Engines (_engines, ICollection<Engine>) Collection ToDependent Engine Inverse: EngineSupplier PropertyAccessMode.Field
    Keys: 
      Id PK
  EntityType: Gearbox
    Properties: 
      Id (int) Required PK AfterSave:Throw ValueGenerated.OnAdd
      EngineId (no field, Nullable<int>) Shadow FK Index
      Name (string)
    Keys: 
      Id PK
    Foreign keys: 
      Gearbox {'EngineId'} -> Engine {'Id'} ToDependent: Gearboxes
    Indexes: 
      EngineId
  EntityType: Location
    Properties: 
      EngineId (no field, int) Shadow Required PK FK AfterSave:Throw ValueGenerated.OnAdd
      Latitude (double) Required Concurrency
      Longitude (double) Required Concurrency
    Keys: 
      EngineId PK
    Foreign keys: 
      Location {'EngineId'} -> Engine {'Id'} Unique Ownership ToDependent: StorageLocation
  EntityType: Sponsor
    Properties: 
      Id (int) Required PK AfterSave:Throw ValueGenerated.OnAdd
      ClientToken (no field, Nullable<int>) Shadow Concurrency
      Discriminator (no field, string) Shadow Required
      Name (string)
      Version (no field, byte[]) Shadow Concurrency BeforeSave:Ignore AfterSave:Ignore ValueGenerated.OnAddOrUpdate
    Keys: 
      Id PK
  EntityType: SponsorDetails
    Properties: 
      TitleSponsorId (no field, int) Shadow Required PK FK AfterSave:Throw ValueGenerated.OnAdd
      ClientToken (no field, Nullable<int>) Shadow Concurrency
      Days (int) Required
      Space (decimal) Required
      Version (no field, byte[]) Shadow Concurrency BeforeSave:Ignore AfterSave:Ignore ValueGenerated.OnAddOrUpdate
    Keys: 
      TitleSponsorId PK
    Foreign keys: 
      SponsorDetails {'TitleSponsorId'} -> TitleSponsor {'Id'} Unique Ownership ToDependent: Details
  EntityType: Team
    Properties: 
      Id (int) Required PK AfterSave:Throw
      Constructor (string)
      ConstructorsChampionships (int) Required
      DriversChampionships (int) Required
      EngineId (no field, Nullable<int>) Shadow FK Index
      FastestLaps (int) Required
      GearboxId (Nullable<int>) FK Index
      Name (string)
      Poles (int) Required
      Principal (string)
      Races (int) Required
      Tire (string)
      Version (no field, byte[]) Shadow Concurrency BeforeSave:Ignore AfterSave:Ignore ValueGenerated.OnAddOrUpdate
      Victories (int) Required
    Navigations: 
      Chassis (_chassis, Chassis) ToDependent Chassis Inverse: Team PropertyAccessMode.Field
      Drivers (_drivers, ICollection<Driver>) Collection ToDependent Driver Inverse: Team PropertyAccessMode.Field
      Engine (_engine, Engine) ToPrincipal Engine Inverse: Teams PropertyAccessMode.Field
      Gearbox (_gearbox, Gearbox) ToPrincipal Gearbox PropertyAccessMode.Field
    Keys: 
      Id PK
    Foreign keys: 
      Team {'EngineId'} -> Engine {'Id'} ToDependent: Teams ToPrincipal: Engine
      Team {'GearboxId'} -> Gearbox {'Id'} Unique ToPrincipal: Gearbox
    Indexes: 
      EngineId
      GearboxId Unique
  EntityType: TestDriver Base: Driver
  EntityType: TitleSponsor Base: Sponsor
    Navigations: 
      Details (_details, SponsorDetails) ToDependent SponsorDetails PropertyAccessMode.Field

State manager debug view

The state manager is a little mode hidden than the model. To find it, drill down into the ChangeTracker property of the DbContext in your debugger of choice and then look in the StateManager property and expand the DebugView.

image

The short view of the state manager shows:

  • Each entity being tracked
  • Its primary key value(s)
  • The entity state - one of Added, Unchanged, Modified, or Deleted.
  • The values of an foreign key properties

For example:

Engine (Shared) {Id: 1} Unchanged FK {EngineSupplierId: 1}
Location (Shared) {EngineId: 1} Unchanged FK {EngineId: 1}
Team (Shared) {Id: 4} Modified FK {EngineId: 1} FK {GearboxId: <null>}

The long view shows everything in the short view together with:

  • The current value of each property
  • Whether or not the property is marked as modified
  • The original value of the property, if different from the current value
  • The entity referenced by a reference navigation using the referenced entity's primary key value
  • The list if entities referenced by a collection navigation, again using primary key values

For example:

Engine (Shared) {Id: 1} Unchanged
  Id: 1 PK
  EngineSupplierId: 1 FK
  Name: 'FO 108X'
  EngineSupplier: <null>
  Gearboxes: <null>
  StorageLocation: {EngineId: 1}
  Teams: [{Id: 4}]
Location (Shared) {EngineId: 1} Unchanged
  EngineId: 1 PK FK
  Latitude: 47.64491
  Longitude: -122.128101
Team (Shared) {Id: 4} Modified
  Id: 4 PK
  Constructor: 'Ferrari'
  ConstructorsChampionships: 16
  DriversChampionships: 15
  EngineId: 1 FK Modified Originally 3
  FastestLaps: 221
  GearboxId: <null> FK
  Name: 'Scuderia Ferrari Marlboro'
  Poles: 203
  Principal: 'Stefano Domenicali'
  Races: 805
  Tire: 'Bridgestone'
  Version: '0x000000000001405A'
  Victories: 212
  Chassis: <null>
  Drivers: []
  Engine: {Id: 1}
  Gearbox: <null>

Pull requests from the last two weeks

Community contributions

Many thanks to all our contributors!

EF Core

Microsoft.Data.Sqlite

  • Huge documentation overall for Microsoft.Data.Sqlite including lots of new information
    • Connection Strings
    • Data Types
    • Parameters
    • Database Errors
    • Transactions
    • Batching
    • Metadata
    • In-Memory Databases
    • Encryption
    • Online Backup
    • User-Defined Functions
    • Custom SQLite Versions
    • Collation
    • BLOB I/O
    • Interoperability
    • Extensions
    • Using with Entity Framework Core
    • Using with Dapper
    • Compare to System.Data.SQLite
    • Using with Xamarin

Issues remaining for 5.0

The burn-down will return for 5.0 once the plan is ready.

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 ajcvickers changed the title Entity Framework Weekly Status Updates Entity Framework Weekly Status Updates (2019) Jan 10, 2020
@ajcvickers ajcvickers unpinned this issue Jan 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants
You can’t perform that action at this time.