Here is a question I have yet to find a good answer for: What is your tactic for versioning a project's database/schema, especially with EF CodeFirst?
In my last big ASP.NET/EF
project I used a temporary local database (not included in the source control) until I launched. This meant that each programmer always had the latest schema. I wanted a "Hit F5 and go" sort of experience and this gave me just that.
Once the site was launched I locked in a local database and manually wrote upgrade scripts to make sure I could quickly update the production database when pushing a change. It felt wrong at best - I had hoped there would be an automatic way of doing this, but have yet to find one.
I suppose many will suggest the 'Migrations' part of EF, but I don't think this solution is automatic, though I admit I have not looked farther into it than a few blog posts. Regardless, it looks like you're just moving the authoring of SQL scripts into .NET.