1

I'm having trouble making Entity Framework update to the latest migration automatically (conflicts between SimpleMembership and the EF data model) so I've decided to script each migration to SQL then apply that.

However I've run into a problem with introducing the first migration. I have a full migration in my project that I generated by running Add-Migration <migration name> and now I'd like to create a SQL script using Update-Database -Script. However when I run that command EF checks my code and the development database, sees that everything is up to date and doesn't script a new migration. I thought I could use the -SourceMigration switch, but that appears to require a migration before the one you want to reach.

I could simply delete the development database, script the migration, then rerun Add-Migration, but I feel like I must be mistaken in how I'm using migrations.

Improve this question

2 Answers 2

Reset to default
3

Its not really undocumented: See http://msdn.microsoft.com/en-us/data/jj591621 or EF Migration migrate to 0 call initial creates down

The proper usage should be something like be "Update-Database –SourceMigration:$InitialDatabase ..." or "Update-Database –SourceMigration:0" for shorter syntax.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

0

I just found an undocumented solution. Instead of passing a migration name to -SourceMigration simply pass 0 which and you'll get the migrations from before the initial migration.

Improve this answer

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.