Does Database initializer obsolete in EF 6.0 ? And we should use Migration instead of it.

Question

In this tutorial
http://www.asp.net/mvc/overview/older-versions/getting-started-with-aspnet-mvc3/cs/adding-a-new-field
I see such code
public class MovieInitializer : DropCreateDatabaseIfModelChanges<MovieDBContext> {
protected override void Seed(MovieDBContext context) {
var movies = new List<Movie> {
new Movie { Title = "When Harry Met Sally",
ReleaseDate=DateTime.Parse("1989-1-11"),
Genre="Romantic Comedy",
Rating="R",
Price=7.99M},
new Movie { Title = "Ghostbusters ",
ReleaseDate=DateTime.Parse("1984-3-13"),
Genre="Comedy",
Rating="R",
Price=8.99M},
new Movie { Title = "Ghostbusters 2",
ReleaseDate=DateTime.Parse("1986-2-23"),
Genre="Comedy",
Rating="R",
Price=9.99M},
new Movie { Title = "Rio Bravo",
ReleaseDate=DateTime.Parse("1959-4-15"),
Genre="Western",
Rating="R",
Price=3.99M},
movies.ForEach(d => context.Movies.Add(d));
But when I went to https://msdn.microsoft.com/en-us/data/ee712907 I see only migration database
I am newbie at EF. I am focusing on Code First. I have an idea that
DropCreateDatabaseIfModelChanges
and another DataBase initializer is not acutal for EF 6 but it was used in previous version.
On the other hand from names of this
Database initializer is for database initization
Migration for database structure changing
Before learning I decided ask this question
Does Database initializer obsolete in EF 6.0  ? And I should use Database Migration instead of it ?
My .NET Blog with projects and feedback.
Since May 30, 2014 I am waiting for Microsoft fix
these 2 bug. If you know how to speed them up, please help

Answer 1

Hello,
>>Does Database initializer obsolete in EF 6.0?
I do not know why you think so, if the team decides to make the database initializer obsolete, I think they would make a markup as Deprecated, however, there is not such a markup on that method on MSDN document. And the Database initializer method is useful
when we play with automatic migration. In your case, the DropCreateDatabaseIfModelChanges database initialization strategy, would delete the original database and create new one according your new model. Of course, data would be missing. If you are under a
scenario need to make a test to recreate the database frequently, this one should be ok.
Currently, there are four database initialization strategies could be used:
CreateDatabaseIfNotExists<TContext> Class
DropCreateDatabaseAlways<TContext>
DropCreateDatabaseIfModelChanges<TContext>
MigrateDatabaseToLatestVersion<TContext, TMigrationsConfiguration>
You could use one of them for a proper scenario.
Regards.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.