Here's the type of scenario I'm thinking of as well as what I think would be a solution, but I'm not sure if it can be done.
The "previous format" could be different table structure, fields, data types, etc. essentially anything you'd expect a typical migration to be able to handle.
Is that possible?
Is that are reasonable solution?
If so, any pointers on implementation would be appreciated.
Thanks!
No. The crucial hurdle is in this part
Migrations are applied to the context
This is just not possible. Migrations are all about the store model. It compares a hash of the SSDL (Store schema definition language) of a context (edmx) to the hash that is stored in the database. If the hashes are different, the schema differences are analyzed and converted into change actions. Of course these actions are aimed at the store model.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With