This project is read-only.

How is this different from Migratordotnet?

Nov 15, 2009 at 6:13 PM

How is this going to be different from the existing Migratordotnet library?  What will it provide over that framework?

Nov 15, 2009 at 11:44 PM

Good question, actually I didn't know the MigratorDotNet project before. I started this project for my own usage and published it on CodePlex cause I though it might be useful for other people, too.

Mar 26, 2010 at 4:19 PM

And how is it different from RikMigrations (

Seems like we have at least 3 libraries that do quite the same...

Mar 30, 2010 at 4:11 AM
By having a quick look in the source code of the two mentioned libraries I think there is one big difference between NMigrations and the other ones: NMigrations is a deterministic SQL generator, it doesn't care what the underlying database in reality looks like. Actually there is not a single SQL query executed by NMigrations to check the schema of the database. A migration will always generate the same SQL statements. I wanted to have this behavior to avoid rude surprises when applying my migrations to the production server. This comes with the cost of some flexibility, but for my use case this was OK.
Feb 17, 2011 at 12:42 PM

I've just wanted to inform you that in the meantime, we have developed our on framework which is freely available on GitHub:

It also has a deterministic SQL generator, and adds support for CE 4, Oracle, and Teradata. Plus there is support for multi-module (which was very important for us), a strong validation framework and other nice features:

I thought, I'd mention it in case your interested...


Feb 17, 2011 at 8:08 PM

Your project looks very promising ... has some nice features I always wanted to include in NMigrations, but never had the time to do so. Your source code looks pretty nice & clean, too - so congratulations to that great library.


Feb 18, 2011 at 7:31 AM

Thank you! :)