ASP.NET Core 2.0 Code First Migration - New Database

Question

I currently have an ASP.NET Core 2.0 project and I've just implemented code first migrations to the localdb and have around 3 migrations including the initial create. I'm wondering what the correct process is to change to a new database? Is it simply a case of updating the connection string and running the below in the project directory?

dotnet ef database update

My current knowledge is based on the below Microsoft tutorial and I've been using the CLI commands. https://docs.microsoft.com/en-us/aspnet/core/data/ef-mvc/migrations

Answer 1

In answer to my own question, it does appear that running the following command in the existing project directory will build a new database from scratch including all the existing migrations. As long as you update the connection string to the new database and have already implemented migrations on the existing database.

dotnet ef database update

Answer 2

correct process is to change to a new database

Everything depends what you mean by writing this sentence ( I am not sure what "new database" means in it) altough flow looks like this: 1. First you make initial create 2. Then you change something in your code (create some additional fields etc) 3. Then you write "dotnet ef database update" command in CLI to update your current database.