We are following the Entity Framework Code First model and developing a couple of applications. Now we have production/staging/development databases, and I need a good way to ensure changes are properly effected in each of the environments.
The blunt approach is to have the app create an empty database (or deploy an empty database) and then migrate all the necessary data, but this is just a lame way of doing things.
I checked online and there are suggestions for VSDBCMD (?), but we only have VS 2010 prof, so no database projects to speak of.
Any other solution?
If I migrated to EF 4.3 which supposedly has support for migrations, do I need to change anything else in the code?