If you haven’t used Update-Database you can just delete the migration file. If you’ve run the update you should roll it back using Update-Database -TargetMigration “NameOfPreviousMigration” then delete the migration file. Reference: Tips for Entity Framework Migrations
String is a reference type and always nullable, you don’t need to do anything special. Specifying that a type is nullable is necessary only for value types.
Entity Framework 6 added support for multiple DbContexts by adding the -ContextTypeName and -MigrationsDirectory flags. I just ran the commands in my Package Manager Console and pasted the output below… If you have 2 DbContexts in your project and you run enable-migrations, you’ll get an error (as you probably already know): PM> enable-migrations More than … Read more
Here is example of usual Seed approach: protected override void Seed(SecurityModule.DataContexts.IdentityDb context) { if (!context.Roles.Any(r => r.Name == “AppAdmin”)) { var store = new RoleStore<IdentityRole>(context); var manager = new RoleManager<IdentityRole>(store); var role = new IdentityRole { Name = “AppAdmin” }; manager.Create(role); } if (!context.Users.Any(u => u.UserName == “founder”)) { var store = new UserStore<ApplicationUser>(context); var … Read more
It’s because of other projects in your solutions. e.g If you have two projects in your solution as Project A and Project B. If Project A is not successful build and then Project B data migration will fail. So you should unload Project A and add the migration to Project B again. I think this … Read more
All EF commands have this check: if (targetAssembly != migrationsAssembly) throw MigrationsAssemblyMismatchError; targetAssembly = the target project you are operating on. On the command line, it is the project in the current working directory. In Package Manager Console, it is whatever project is selected in the drop down box on the top right of that … Read more
Try this: context.People.AddOrUpdate(p => new { p.FirstName, p.LastName }, people);
This is embarrassing, but maybe this will help out a googler in the future. At the top of the “Package Manager Console” my default project was set to the wrong project. Changing that to my models project fixed it.
It tells you that there is some unprocessed migration in your application and it requires running Update-Database before you can add another migration.
If I’m understanding it right… If you want to start clean: 1) Manually delete your DB – wherever it is (I’m assuming you have your connection sorted), or empty it, but easier/safer is to delete it all together – as there is system __MigrationHistory table – you need that removed too. 2) Remove all migration … Read more