Hi Chris,
Thanks again for considering contributing to EF!
Firstly, here are some of the things we are doing or planning on doing for EF6:
1) Providing a way to change the default schema for a Code First model. Part of this has already been done with the addition of HasDefaultSchema to DbModelBuilder. We are currently working on flowing this default schema through to the history table.
2) Allowing the HistoryContext Code First model (the context we use to access the history table) to be configured in the standard way i.e. via a DbModelBuilder instance. This API will likely hang off DbMigrationsConfiguration - perhaps something like OnHistoryModelCreating.
3) Following on from 1 and 2, dealing with migrating the history table when its configuration changes.
4) Supporting migrating multiple contexts per database.
Secondly, I would like to better understand the exact issues you are running into using Migrations with third-party providers. Specifically, for the issues you call out, it seems like they could both be handled in the provider layer. Which providers are you using for both EF runtime and Migrations?
Cheers,
Andrew.