Migrations: Consider options for improving multi-user experience (team environments)


We have been brainstorming ideas for better dealing with multi-user migrations issues.

Issue: After sync, if the user has local migrations then they will often get a model out of date exception because of out-of-date code-behind metadata...

  • Can we use a git style back-pointer to detect multiple "heads"?
  • Yes, but what do we do with this information?
    • Provider better diagnostics?
    • Implement merge/rebase commands for migrations - seems complex...
Andrew has implemented back-pointers in a local branch.
Closed Mon at 11:31 PM by RoMiller
EF Team Triage: We are transitioning this project to GitHub (https://github.com/aspnet/EntityFramework6). As part of this transition we are bulk closing a large number of issues in order that our new issue tracker will accurately reflect the work that our team is planning to complete on the EF6.x code base.

Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base (https://github.com/aspnet/EntityFramework). Closing a feature request in the EF6.x project does not exclude us implementing the feature in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).

This is a bulk message to indicate that this issue was closed and not ported to the new issue tracker. The reasons for not porting this particular issue to GitHub may include:
• It was a bug report that does not contain sufficient information for us to be able to reproduce it 
• It was a question, but sufficient time has passed that it's not clear that taking the time to answer it would provide value to the person who asked it 
• It is a feature request that we are realistically not going to implement on the EF6.x code base
Although this issue was not ported, you may still re-open it in the new issue tracker for our team to reconsider (https://github.com/aspnet/EntityFramework6/issues). We will no longer be monitoring this issue tracker for comments, so please do not reply here.


jjwilliams wrote Dec 20, 2013 at 8:40 PM

How did that local back-pointer branch turn out?