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.