#Learning about Entity framework Core
I'm familiar with EF6 but I'll try to cover the basics in what I research for EF Core
EF Core includes a set of additional commands for the dotnet CLI, starting with dotnet ef. In order to use the dotnet ef CLI commands, your application’s .csproj file needs to contain the following entry:
The .NET Core CLI tools for EF Core also require a separate package called Microsoft.EntityFrameworkCore.Design
I'm using the InMemory Provier as a test. We will not use this for our demo.
Just read something about integrating the CLI->
Add node as shown below. This is an extra step you need to perform in order to execute EF Core 2.0 commands from dotnet CLI in VS2017 This could help with problems I'm having with docfx.
While Generating the DBContext constructor, I came across the following error.
NotNullAttribute not accesible due it's defined as Internal in its assembly'. Apparantly this is a Resharper helper class for code validation. But if you are not using Resharper or don't want to have this validation happen, just remove the attribute, it has not code behind. It's just a marker of Resharper to validate the code.
Damn no migration for InMemory, I'll those those tests for later.
Hmm no Many 2 Many relations without creating the mappingtable as an entity. Could be a deal breaker to advice use of EFCore ( and .NET Core) for projects with many such relations.
I'll add more info as I learn about this.
https://docs.microsoft.com/en-us/ef/core/get-started/install/
Problem when DbContext is in a .Net Standard project: https://stackoverflow.com/questions/44430963/is-ef-core-add-migration-supported-from-net-standard-library
https://docs.microsoft.com/en-us/ef/core/modeling/#methods-of-configuration https://docs.microsoft.com/en-us/aspnet/core/data/ef-mvc/complex-data-model https://docs.microsoft.com/en-us/aspnet/core/data/ef-mvc/migrations#introduction-to-migrations