I see this happening when I do not add my DBSet to my DbContext class, which is associated with the migration configuration file.
Although, perhaps this is not so, since we see that Asker has included the line:
public DbSet<ReturnedTransactions> ReturnedTransactions { get; set; }
However, this is what you need to check when an empty migration class is returned.
Brian merrell
source share