如何在.NET Core DbContext.OnConfiguring中检测EF迁移程序并切换连接方式

Great question! You’re on the right track wanting to use different authentication methods for EF Core design-time commands (like dotnet ef migrations add) versus regular application runtime. The approach you tried with options.Context.IsModelBuilder isn’t the standardized way, but there’s an official, reliable method to handle this scenario cleanly.

The Standardized Approach: Check the EFCORE_DESIGN_TIME Environment Variable #

EF Core automatically sets the EFCORE_DESIGN_TIME environment variable to true when running design-time commands (migrations, scaffold, database updates, etc.). You can read this variable directly in your OnConfiguring method to switch between authentication modes.

Example Implementation #

protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
{
    bool isDesignTime = Environment.GetEnvironmentVariable("EFCORE_DESIGN_TIME") == "true";

    string connectionString;
    if (isDesignTime)
    {
        // Use integrated security for migrations/scaffolding workflows
        connectionString = "Server=***;Database=***;Integrated Security=True;";
    }
    else
    {
        // Use username/password for regular application runtime
        connectionString = "Server=***;Database=***;user id=***;password=***;";
    }

    optionsBuilder.UseSqlServer(connectionString);
}

Alternative: Use a Design-Time DbContext Factory (Official Recommendation) #

For more complex configuration scenarios, EF Core recommends using an IDesignTimeDbContextFactory<T> implementation. This lets you fully separate design-time configuration from your runtime DbContext, eliminating the need for conditional logic in OnConfiguring entirely.

Example Factory Implementation #

public class YourDbContextDesignTimeFactory : IDesignTimeDbContextFactory<YourDbContext>
{
    public YourDbContext CreateDbContext(string[] args)
    {
        var optionsBuilder = new DbContextOptionsBuilder<YourDbContext>();
        // Configure design-time specific connection string here
        optionsBuilder.UseSqlServer("Server=***;Database=***;Integrated Security=True;");

        return new YourDbContext(optionsBuilder.Options);
    }
}

When you run dotnet ef commands, EF Core will automatically use this factory to create the DbContext instance. Your runtime OnConfiguring can then focus solely on production authentication without any conditionals.

Why This Works #

Both methods align with EF Core’s official design-time workflow. The environment variable check is lightweight and ideal for simple conditional logic, while the factory pattern offers cleaner separation for more complex setups (like loading configuration from different sources).

内容的提问来源于stack exchange，提问作者André Reichelt