EF add-migration generates empty migration

Question

I added into my model a new table:

public DbSet<ReturnedTransactions> ReturnedTransactions { get; set; }

And i want my migrations to generate that table for me, so i did:

PM> Add-migration returnedTransactions

And it generated

public partial class returnedTransactions : DbMigration
{
    public override void Up()
    {
    }

    public override void Down()
    {
    }
}

How do i force this thing to generate proper code for me?

What fields are in your table? Can you show the class where you define the table? — Kirsten, Feb 24 '13 at 03:14
Well it's a class with a bunch of fields, why does that matter? — ojek, Feb 24 '13 at 03:45
It's possible that `ReturnedTransactions` was already created because it is referenced from another entity via foreign keys. — Steven V, Jan 17 '14 at 14:09
Possible duplicate of [EF migration shows empty Up() Down() methods](http://stackoverflow.com/questions/22708519/ef-migration-shows-empty-up-down-methods) — Matyas, May 31 '16 at 06:17

score 3 · Answer 1 · answered Oct 16 '15 at 15:19

I see this happen when I do not add my DBSet Entity to my DbContext class that is associated with the Migration Configuration file.

Although, it may not be the case here as we can see that the Asker included the line:

public DbSet<ReturnedTransactions> ReturnedTransactions { get; set; }

Still, this is something one should check when they are returned an empty migration class.

score 1 · Answer 2 · edited Jan 17 '14 at 14:05

1

Clear out the _MigrationHistory table.

edited Jan 17 '14 at 14:05

TLama

75,147
17
214
392

answered Jan 17 '14 at 13:07

DickP

21
1

6

I would recommend against just randomly cleaning out `__MigrationHistory` table. That will cause Entity Framework to think that the migrations have run, and the tables have not been created. Then when Entity Framework runs the migrations, it will throw errors about the tables or columns existing. The better way is to use `Update-Database -Target:0` or similar command to remove things. – Steven V Jan 17 '14 at 14:07

score 1 · Answer 3 · answered Aug 15 '22 at 09:14

Check the created table in the "ApplicationDbContextModelSnapshot" class, This class is added to the Migrations folder when the first migration is made and updated with each subsequent migration. Try to clear the new table if it's there or deletes this class. It worked for me.

score 0 · Answer 4 · answered Dec 10 '15 at 17:15

0

I just had this problem and I added -Force to the Add-Migration command and it worked.

answered Dec 10 '15 at 17:15

Dougmany

11
1

score 0 · Answer 5 · answered Dec 17 '20 at 19:03

0

That may sound stupid, but do you have all needed packages installed? I have had the same problem and it turned out that a packages was missing, I think it was Microsoft.AspNetCore or Mircosoft.AspNetMVC.

answered Dec 17 '20 at 19:03

maxE

359
1
11

score 0 · Answer 6 · answered Dec 02 '21 at 23:16

0

Adding to the above answer, for me I had to add Microsoft.AspNetCore.Identity.EntityFrameworkCore through NuGet in an another project, which is connected with the one containing the database context.

answered Dec 02 '21 at 23:16

Kristiyan Ivanov

53
1
8

EF add-migration generates empty migration

6 Answers6

Linked