I noticed there are some changes planned for Migrations API, mainly I'm interested in support for multiple contexts. Is there any information regarding how it will be implemented?
Also it seems like there needs to be a way to redefine __MigrationHistory or the way the schemas are checked and make migrations a little more extensible. Right now it is not possible to extend or change the way migration works since most of the API's are internal.
The migration I'm looking for is the one where I control the version of the schema (I don't need to save and examine serialized schema every time i perform update, just checking the version and migration update history) and I have no need for any automatic migrations or scaffolding (except initialcreate). Unfortunately I can't extend DbMigrator or write my own (except as part of the EntityFramework library).
I'm willing to contribute but would like some guidance on if there is a plan to address the above concerns so I can move in the same general direction EF is going.