Entity Framework Core 1.1 Announced

This news talks about the announcement of Entity Framework Core 1.1 and its associated features.

A lightweight, extensible, and cross-platform version of Entity Framework is known as Entity Framework Core (EF Core), which follows the same release cycle as .NET Core.
1.1 is imbibed with a feature that revolves around addressing issues that prevent folks from adopting EF Core, which comprises of fixing bugs and adding some of the critical features that are not yet implemented in EF Core. As far as bug fixes are concerned, bug fixes included in the 1.1 release are over 100. EF Core LINQ provider has been improved which entices more queries to successfully execute, with more logic being evaluated in the database (rather than in memory).
One of the more common requests for EF Core is DbSet.Find(…), which entices you to easily query for an entity based on its primary key value. If the entity is already loaded into the context, then it is returned without querying the database. HasField(…) method has an ability, which can be useful for read-only properties, or data that has Get/Set methods rather than a property. If you want to load the contents of a navigation property for an entity that is tracked by the context, Explicit loading is there is to help you. EntityEntry comprises of Reload(), GetModifiedProperties(), GetDatabaseValues(). To retry failed database commands, connection resiliency is always there to provide the support.
In SQL Server, the feature of Memory-Optimized Tables is phenomenal; as it provides you an opportunity to specify that the table an entity is mapped to is memory-optimized. One needs to upgrade his provider package. If he is using one of the database providers shipped by the EF Team (SQL Server, SQLite and InMemory). On the other hand, when third party database provider is being used, one needs to verify if they have released an update that depends on 1.1.0, else only EF Core relational components needs to be upgraded.
Since tooling has not reached its initial stable release, one needs to make sure that tooling is versioned as 1.0.0-preview4. For the users of ASP.NET Core and the dotnet ef commands, if the person is using new Microsoft.EntityFrameworkCore.Tools.DotNet package in place of the Microsoft.EntityFrameworkCore.Tools package from 1.0., then he is required to update the tools section of project.json.