![]() ![]() ![]() I could automate this into the process for the product release, but it would take too much work and might lead to problems. The drawback is the same as with method 1. This is feasible, however I must teach other developers to make sure to migrate the product version.Ĭreate an empty migration for every significant product release. Include the product version in the migration's name. So here's my inquiry: Is there a method to link our product version to the row for migration history? The issue is that my coworkers are unaware of which database migration corresponds to which release of our software. Therefore, we employ an internal tool to upgrade or downgrade the EF database whenever we need to support an earlier version. ![]() All customers have a support term of x months, therefore they are using various product versions and have undergone various EF migrations for their individual databases.Ī few other coworkers assist me with product support, and they often handle customer support phone calls for various product versions.ĭue to worries about data loss, the product only enables updating EF databases downgrading is not supported. We have many versions of our software products installed on client computers, and I'm utilising EF6 with one of them (a network-based web application).
0 Comments
Leave a Reply. |