Hello
On my first job, I worked using code-first with the Entity Framework 4. At this time, I saw a limitation on it: the generated migrations only ran in order. For example, if two people are working with persistence in my branch, generated migrations may not run. This was due to a migration with less than the last timestamp registered in the database not being executed.
Shortly thereafter, I left the company and from there I only worked with NHibernate and migrations using MigSharp. However, for the sake of organization and practicality I have always preferred Entity and I have been thinking about the possibility of implementing it in new projects of the company. The issue of this mandatory migration of migrations would not work here: If the master branch undergoes a last-minute persistence fix to solve problems already in production, the development branch would have to change the entire timestamp of the migrations already created and that are not yet in the master, or else the migrations would not be executed.
As I said, I had this problem in Entity Framework 4. My question is: In the new versions of the Entity Framework is there any configuration that allows the execution of migrations without a mandatory order? If not, what is the most 'professional' way of avoiding problems such as these occurring during the development of tasks alongside last-minute fixes or even continuous integration processes when pushing?
Thank you!