EF Code First控制台应用无法为数据库填充数据求助

Hey Daniel, let's figure out why your seed data isn't showing up even after running update-database. Based on the code snippet you shared, here are the key areas to check:

1. Verify Your ApplicationDbInitializer Implementation #

You’ve set up an initializer with Database.SetInitializer(new ApplicationDbInitializer()), but the critical part is whether this class properly overrides the Seed method to insert data. If you haven’t already, your initializer should inherit from one of EF’s base initializer classes and explicitly add data + save changes. Here’s an example of a working setup:

namespace ToDoApp.Models
{
    public class ApplicationDbInitializer : DropCreateDatabaseIfModelChanges<ApplicationDbContext>
    {
        protected override void Seed(ApplicationDbContext context)
        {
            // Add your test data here
            context.Tests.AddRange(new List<TestModel>
            {
                new TestModel { Name = "First Test", Description = "Sample seed data" },
                new TestModel { Name = "Second Test", Description = "More sample data" }
            });

            // Don't forget this line! It commits the changes to the database
            context.SaveChanges();
        }
    }
}

• If your initializer doesn’t include SaveChanges(), the data will never be persisted.
• If you’re using a different initializer type (like CreateDatabaseIfNotExists), note that it only runs once when the database is first created—so if your database already exists, the seed won’t re-run unless you delete the database or switch to DropCreateDatabaseAlways (good for development only).

2. Force the Initializer to Run (If Needed) #

Sometimes the initializer won’t trigger automatically in console apps. You can explicitly initialize the database when your app starts to ensure the seed runs:

In your Program.cs (or entry point):

using ToDoApp.Models;
using System.Data.Entity;

class Program
{
    static void Main(string[] args)
    {
        // Ensure the initializer runs
        Database.SetInitializer(new ApplicationDbInitializer());
        using (var db = new ApplicationDbContext())
        {
            db.Database.Initialize(true); // Forces initialization even if the database exists
        }

        // Rest of your app code
    }
}

3. Check Your Connection String #

Your context uses base("ToDoApp"), which means EF is looking for a connection string named "ToDoApp" in your App.config file. Double-check that this string points to the database you’re checking—sometimes console apps can connect to unexpected LocalDB instances or SQL Server databases, making it look like the seed didn’t run when it actually did.

Example connection string in App.config:

<connectionStrings>
    <add name="ToDoApp" 
         connectionString="Data Source=(LocalDB)\MSSQLLocalDB;AttachDbFilename=|DataDirectory|\ToDoApp.mdf;Integrated Security=True" 
         providerName="System.Data.SqlClient" />
</connectionStrings>

4. Ensure TestModel Has a Valid Schema #

EF requires entities to have a primary key to create a valid table. Make sure your TestModel includes a primary key property (EF automatically recognizes properties named Id or [ClassName]Id):

public class TestModel
{
    public int Id { get; set; } // Required primary key
    public string Name { get; set; }
    // Other properties
}

Without a primary key, EF might not create the table properly, leading to silent failures when inserting seed data.

5. Check Package Manager Console Output #

When you run update-database, look closely at the output in the Package Manager Console. Are there any error messages (like permission issues, model validation errors, or connection failures)? These can often explain why the seed data isn’t being inserted even if the command appears to run successfully.

内容的提问来源于stack exchange，提问作者Daniel