title: EF 4.3 Auto-Migrations with multiple DbContexts in one database
body: <p>I'm trying to use EF 4.3 migrations with multiple code-first DbContexts. My application is separated into several plugins, which possibly have their own DbContext regarding their domain. The application should use one single sql-database. </p>
  
  <p>When I try to auto migrate the contexts in an empty database, this is only successful for the first context. Every other context needs the AutomaticMigrationDataLossAllowed-Property set to true but then tries to drop the tables of the previous one. </p>
  
  <p>So my question is: </p>
  
  <ul>
  <li>How can I tell the migration-configuration just to look after the tables defined in their corresponding context and leave all others alone?</li>
  <li>What is the right workflow to deal with multiple DbContexts with auto-migration in a single database?</li>
  </ul>
  
  <p>Thank you!</p>