EF Core is a modern object-database mapper for .NET. It supports LINQ queries, change tracking, updates, and schema migrations.
MIT License
Published by danroth27 almost 8 years ago
Published by danroth27 about 8 years ago
Published by danroth27 over 8 years ago
Published by danroth27 over 8 years ago
xml
, hierarchyid
, geography
, geometry
, etc (#3076)dbcontext scaffold
has two -s options (#4677)Published by danroth27 almost 9 years ago
Published by danroth27 about 9 years ago
Published by danroth27 about 9 years ago
Published by danroth27 about 9 years ago
Published by danroth27 over 9 years ago
Published by danroth27 over 9 years ago
EF7 introduces some significant changes and improvements over EF6.x and therefore the pre-release phase of EF7 is much longer than other recent releases. We’ve made significant progress since our last pre-release, but if you decide to try out EF7 then please bear in mind that this preview is designed to give you an idea of what the experience will be like and there are still a number of limitations and missing features that will be addressed before RTM.
If you aren’t comfortable working with a prerelease that is still very much in-flux then don’t worry… there will be plenty of opportunity to try out pre-release EF7 once it is much more stable.
Beta 4 can be used in the following types of applications
Currently you can target SQL Server or our in-memory store (designed to help with testing). These providers are available in the EntityFramework.SqlServer and EntityFramework.InMemory NuGet packages.
We are working on other providers that will be available for the next prerelease (more on that below).
Here is a rough guide to what currently works in Beta 4. Most of these features are a work-in-progress and still have limitations.
Here are some of the areas we are currently working on (or working with other development teams to deliver). You can see many of these features already underway in our working code base.
Providers
There is work underway to enable the following database providers. We’ve also had contact with many other providers who are planning to provide EF7 support.
Platforms
We are working to enable EF7 use on the following platforms:
Features
Here are a number of the cross-cutting features we are currently working on. This isn’t all we will be doing for RTM, just what’s currently underway.
Published by danroth27 over 9 years ago
Published by danroth27 almost 10 years ago
Published by danroth27 almost 10 years ago
Published by danroth27 about 10 years ago
Published by rowanmiller about 10 years ago
Since Alpha 2 the majority of our work has been around adding or improving the core components of the EF7 code base and improving test coverage.
These release notes only list the more prominent changes/improvements/additions that affect the functionality available to developers using EF7.
Please bear in mind that this preview is designed to give you an idea of what the experience in EF7 will be like and you will quickly hit limitations if you deviate from any sample code and/or try to use advanced features. The API surface will also change significantly in future previews.
In Alpha 3 we made progress on our various database providers:
Query Pipeline: The component that translates a LINQ query into a store specific query and then passes results back to EF.
Update Pipeline: The component that translates information from the ChangeTracker into store specific update commands (i.e. INSERT/UPDATE/DELETE on a relational database).
DDL Pipeline: The component that creates schema objects in the database (i.e. Tables, Columns, etc. in a relational database).
We implemented more of the functionality that detects changes to the values stored in the properties of your objects. This also includes automatically 'fixing up' the values stored in navigation and foreign-key properties when EF detects that one of them has changed.
We enabled the migrations commands for non-ASP.NET vNext applications. If you install the EntityFramework.Design NuGet package, the Add-Migration and Update-Database commands will be available in Package Manager Console. Note that the Enable-Migrations command is no longer required or available.
Published by rowanmiller over 10 years ago
Since Alpha 1 the majority of our work has been around adding or improving the core components of the EF7 code base and improving test coverage.
These release notes only list the more prominent changes/improvements/additions that affect the functionality available to developers using EF7.
Please bear in mind that this preview is designed to give you an idea of what the experience in EF7 will be like and you will quickly hit limitations if you deviate from any sample code and/or try to use advanced features. The API surface will also change significantly in future previews.
We renamed most of the data access related packages to better align with the existing EF6 package names.
The new names for the top level packages you would install in a project are listed below. We also renamed a number of the infrastructure packages, but they will be pulled in as needed when you install one of the packages listed below.
In Alpha 2 we made progress on our various database providers:
SELECT * FROM xyz
query as we did in Alpha 1. These include filtering, sorting, projection (i.e. selecting a subset of columns), and others. We also made general improvements to the DDL Pipeline and the Update Pipeline.Query Pipeline: The component that translates a LINQ query into a store specific query and then passes results back to EF.
Update Pipeline: The component that translates information from the ChangeTracker into store specific update commands (i.e. INSERT/UPDATE/DELETE on a relational database).
DDL Pipeline: The component that creates schema objects in the database (i.e. Tables, Columns, etc. in a relational database).
More of the asynchronous query operators (such as ToListAsync()
, FirstAsync()
) are now functional.
As we've worked on targeting no-relational data stores it became apparent that the fine grained DDL methods on DbContext.Database
(such as Exists()
, HasTables()
, etc.) were not applicable to most non-relational databases. We now have more generic EnsureCreated()
and EnsureDeleted()
methods on DbContext.Database
.
The relational specific methods are available by using the AsRelational()
extension method that is available when targeting a relational provider. For example, myContext.Database.AsRelational().Exists()
. If you attempt to use AsRelational()
when targeting a non-relational database, it will throw.
Note that the DDL methods on DbContext.Database
are being widely used in samples etc. at the moment because Migrations is not yet available to handle database creation and alteration. Once Migrations is available, these methods should only be used to create databases for unit testing etc.