❔ Code in EF Migrations?
My app will need to update the database when you run a newer version of the app than before. This a very common issue and you usually use EF (Core) to migrate the database. What about non-db tasks? For example what if I want to move my files from one storage location to another? I could put the code into the db migration and it would most likely work.
I don't think that's the best approach because EF migrations are designed to migrate the database and nothing else. What's an alternative to that approach?
I don't think that's the best approach because EF migrations are designed to migrate the database and nothing else. What's an alternative to that approach?
