Porting an EF6 EDMX-Based Model to EF Core
EF Core does not support the EDMX file format for models. The best option to port these models, is to generate a new code-based model from the database for your application.
Install EF Core NuGet packages
Microsoft.EntityFrameworkCore.Tools NuGet package.
Regenerate the model
You can now use the reverse engineer functionality to create a model based on your existing database.
Run the following command in Package Manager Console (Tools –> NuGet Package Manager –> Package Manager Console). See Package Manager Console (Visual Studio) for command options to scaffold a subset of tables etc.
Scaffold-DbContext "<connection string>" <database provider name>
For example, here is the command to scaffold a model from the Blogging database on your SQL Server LocalDB instance.
Scaffold-DbContext "Server=(localdb)\mssqllocaldb;Database=Blogging;Trusted_Connection=True;" Microsoft.EntityFrameworkCore.SqlServer
Remove EF6 model
You would now remove the EF6 model from your application.
It is fine to leave the EF6 NuGet package (EntityFramework) installed, as EF Core and EF6 can be used side-by-side in the same application. However, if you aren't intending to use EF6 in any areas of your application, then uninstalling the package will help focus compiler errors on pieces of code that need attention.
Update your code
At this point, it's a matter of addressing compilation errors and reviewing code to see if the behavior changes between EF6 and EF Core will impact you.
Test the port
Just because your application compiles, does not mean it is successfully ported to EF Core. You will need to test all areas of your application to ensure that none of the behavior changes have adversely impacted your application.
EF Core does not support the
EntityClient provider and therefore any EntitySQL queries must be migrated to LINQ or
Furthermore, there is no support for EntityClient connection strings.
For more considerations, read the complete guide to differences between EF6 and EF Core.