Let's add non-nullable date property:

public DateTime DateAdded { get; set; }

This is how the new property looks in VB.NET:

Property DateAdded() As DateTime

We want this new column to default to the current date. If we update our database again, we will see that the new column will have a default of 1/1/1900. This is not what we want, and here is when we need to switch to explicit migrations. In general, explicit migrations are more flexible than automatic ones. Although we need to write more code, we have far more control over the flow of migrations, their names, and the rollback process. If we start mixing the two approaches, we may get confused. For example, we would have to search the project to see if a column was added by automatic or manual migration. So, in order to provide consistency and for maintenance purposes, we may want to standardize on explicit migrations, and at that point, we should disable automatic migrations.

In order to get started with this approach...