ef-migrations

I have 2 questions: 1) How can I run Seed() method from the package-manager console without updating-database model? 2) Is there a way how to call Seed() method in the code? Thx for any advice. Answering your first question. Create a Migration by running add-migration SeedOnly Clear out all Up() and Down() code generated if there was any pending changes public partial class SeedOnly : DbMigration { public override void Up() { } public override void Down() { } } Then you can Target a Specific Migration by running update-database -TargetMigration SeedOnly in the Package Manager console After

I'm testing with EF 4.3 (beta) I have some new classes which should generate db tables and columns. From a old project i have some old tables in my schema, which i want to access via EF. All Classes are declared. For accessing the old table, there is a poco which is mapped. The db migrations tries to create that old table, too. How can it set that this class/table is not part of the migration, but part of the ef model? xxx.OnModelCreating() { modelBuilder.Ignore<myOldTableClass>(); } removes the entire class from model. finally i can't use it for access via dbContext. i like to use automatic

I use entity framework migration (in Automatic migration mode). Everything is Ok, but I have one question: How should I seed data when I have many to many relation. For example I have two model classes: public class Parcel { public int Id { get; set; } public string Description { get; set; } public double Weight { get; set; } public virtual ICollection<BuyingItem> Items { get; set; } } public class BuyingItem { public int Id { get; set; } public decimal Price { get; set; } public virtual ICollection<Parcel> Parcels { get; set; } } I understand how to seed simple data (for PaymentSystem class)

I am adding a new migration but this message shows: Unable to generate an explicit migration because the following explicit migrations are pending: [201203170856167_left]. Apply the pending explicit migrations before attempting to generate a new explicit migration. Can any one help me? It tells you that there is some unprocessed migration in your application and it requires running Update-Database before you can add another migration. I had the same problem. Apparently entity framework generates this error when it's unable to connect to the database. So make sure that you're able to access it

According to this blog post most companies using EF Migrations are supposedly not updating the database schema of production databases with EF migrations. Instead the blog post's author recommends to use Schema update scripts as part of the deployment process. I've used Schema update scripts for a few years now and while they work, I was planning to use EF migrations instead in the future for the following reasons: Faster deployment, less downtime A simpler deployment procedure Much easier migration of existing data than it would be possible with T-SQL A more comprehensible syntax of the