ayr-ton
Reputation: 363
How to avoid migrations in model first database with Entity Framework 5 and code first entities?
I started an ASP.NET MVC 4 project with an existing database and for map the existing models I created a ADO.NET Entity Data Model called Legacy.edmx. For my new entities, I'm using code first in meaning to use migrations and in-model validations. Some entities have foreign keys from auto generated entities from ADO.
The problem is, if I try to generate migrations it tries to create all the tables again from Legacy.edmx.
How to avoid this behavior? Or, theres another approach for make this scenario work?
Upvotes: 1
Views: 226
Answers (1)
Related Questions
- Entity Framework implement Code first Migrations and prevent data loss
- How to change models without losing data in production in Entity Framework 6 Code-First?
- How to avoid recreate an existing database using automatic Code First Migration
- Entity Framework Automatic Migrations Existing Database
- How use migrations in ASP.net MVC Entity Framework using DB First
- Entity Framework 6 CodeFirst/DatabaseFirst migration data preservation?
- EF Code First Migrations for multiple databases
- Entity Framework 5 Migrations: Setting up an initial migration and single seed of the database
- ASP.NET MVC 4 Code first migrations after deployment
- EF5 Code First Many to Many with Migrations