I've noticed that ASP.NET Zero/ABP is still adding EF migrations to the EFCore project as of earlier this year. From time to time we update the core ASP.NET Zero framework by merging the latest code changes into our development branch and reconciling any conflicts. For the most part we try not to touch any code files that are part of the framework, but we do have to add our own migrations from time to time. Eventually we're going to find ourselves in a position where ANZ/ABP has added a migration with a timestamp prior to one of our own custom migrations, and upon merging and running update-database, it's not going to work. Is there a best practice in place for handling this situation?
1 Answer(s)
-
1
Hi @tusksoft
You have to delete our migration file and generate a new one for yourself. I couldn't think of a better approach.
