I am running an application that uses custom migrations (the auto generated ones don't fit my requirements). I am trying to understand how to control in which order the Entity Framework will run those migrations. I read on some places that using timestamp on the file names will do it, but that does not work. (it runs 20190131153312_bla before 20190131153208_bla2, for example)
No matter where I look I can't seem to find information on this subject... can anyone help?
Migration file and class names doesn't matter.
EF Core tools prepend timestamp to the user supplied migration names in order to ensure proper string ordering.