3 ms·
+1 for code-first migrations. It's a bit of a learning curve, but the effort is worth it imo.
by kerryritter 7y ago
+1 for code-first migrations. It's a bit of a learning curve, but the effort is worth it imo.
- mmusc 7y agoI prefer dB first. Create an SQL project that defines the schema. It automatically compares the schema with your current dB schema and auto generates a migration script for you. Then update entities from the dB. Few steps involved but avoids writing and maintaing migrations yourself.
- breakingcups 7y agoCode-first does this too, but based on a schema you define in your code and not in your DB.
- NicoJuicy 7y agoI would like to suggest code-first, at least try it once. I don't want to go back to any sort of migrations outside of this.