Updating the database from model changes
Entity Framework includes a migrations API since its Code First (4.1) version. What it does is, allows us to have named schemas for our code first model, that is, for the current state of the POCO model – the classes that compose it and their properties – we can create a named "bookmark". As we improve our model, we can create additional migrations, and keep "bookmarking" them. Whenever we want, we can ask the migrations API to apply them to the database.
Getting ready
We will be using NuGet Package Manager to install the Entity Framework Core 1 package, Microsoft.EntityFrameworkCore
. We will also be using a SQL Server database for storing the data, so we will also need Microsoft.EntityFrameworkCore.SqlServer
.
Finally, xunit
is the package we will be using for the unit tests and dotnet-text-xunit
adds tooling support for Visual Studio. Note that the UnitTests
project is a .NET Core App 1.0 (netcoreapp1.0), where Microsoft.EntityFrameworkCore.Design
is...