title: How do I generate an EF6 database with migrations enabled, without using update-database?
body: <p>In EF5, I relied on the fact that I could recreate my database from the model using <code>Database.CreateIfNotExists()</code></p>
  
  <p>I would generate Migrations as needed, but never check them in to source control (since they tended to be artifacts of the development cycle)   Each developer would then delete and recreate their own databases, from the model as needed.  </p>
  
  <p>Then, we would generate migrations by comparing branches of our code, and get the SQL, to apply to production or other shared databases.</p>
  
  <p>This workflow no longer seems to work, as there is no way to generate a database from scratch when migrations are enabled, without first generating all the migrations and then calling update-database.  Since calling add-migration modifies the csproj file, this makes my scripts (which allow us to easily switch branches) unusable.</p>
  
  <blockquote>
    <p>Migrations is enabled for context 'ApplicationDbContext' but the database does not exist or contains no mapped tables. Use Migrations to create the database and its tables, for example by running the 'Update-Database' command from the Package Manager Console.</p>
  </blockquote>
  
  <p>Is there any way to revert to EF5 behavior where Database.Create will create the current version of the db?</p>