title: Use CreateDatabaseIfNotExists with Code First Migration?
body: <p>In my project, current approach is to create database if not already exists using <code>CreateDatabaseIfNotExists</code> and doing seeding initial data from that <code>Intializer</code> as well. I also added Code First Migration support after upgrade to Entity 4.4, so that in the future when we change the modle/database structure we can update client side database without drop their exist database. </p>
  
  <p>However it didn't seems to working well, for example, I am now stuck on design time where forms wouldn't load and the error message is something like <code>The model backing the 'myEntities' context has changed since the database was created. Consider using Code First Migrations to update the database (http://go.microsoft.com/fwlink/?LinkId=238269).</code>. But the model and database is indeed the updated version, just seems Migration didn't recognize the database generated by <code>CreateDatabaseIfNotExists</code>, but at the same time all seems working well at run time. </p>
  
  <p>Also after that I noticed that if I let <code>CreateDatabaseIfNotExists</code> initialize a database, <code>Add-migration</code> afterwards will fail and complain that <code>pending migration</code> and ask me to do a <code>update-database</code>. When I try to do a the <code>update-database</code>, it will fail as well because the migration path seems assume the database is in initial setup state and will trying to running all the migration scripts while none should be run as the database generated by <code>CreateDatabaseIfNotExists</code> is indeed sync with current model and should not be migrated at all. </p>