Migrations aren't a particularly solved problem in .NET imo. (Bad previous experience with nhibernate and migrations of our team member made us skip it) Curren

Migrations aren't a particularly solved problem in .NET imo. (Bad previous experience with nhibernate and migrations of our team member made us skip it) Currently, we are using MigratorDotNet (it meant writing sql to define Up and Down manually). We ended up with a custom implementation for doing the orm. (battle scars and hence the above question) Yes, I do understand the impedance mismatch for true orm mapping but I sincerely hope to avoid "doing this by hand" until absolutely necessary.