如何结合Entity Framework 6 Code First与DbUp实现数据库迁移？

Great question! I’ve dealt with this exact annoyance of cluttering my solution with temporary migration files before—here are a few cleaner workflows to get the best of both EF’s model-to-SQL generation and DbUp’s reliable schema deployment, without the extra file cleanup steps:

1. Use a Temporary Output Directory for EF Migrations #

Instead of letting Add-Migration drop files directly into your solution, redirect the generated migration to a temporary folder outside your project structure. This keeps your solution clean, and you can easily delete the temp files afterward (or automate the cleanup).

Here’s the step-by-step:

• Run this in the Visual Studio Package Manager Console to create the migration in a temp folder:

  Add-Migration TempMigration -OutputDir "C:\Temp\EFMigrationTemp"
  

• Generate the full SQL script (including the __MigrationHistory insert) with:

  Update-Database -Script -SourceMigration:0 -TargetMigration:TempMigration
  

• Copy the generated SQL from the output window, paste it into a new numbered .sql file in your DbUp scripts folder (e.g., 0003_AddOrderStatusColumn.sql).
• Delete the temp migration files from C:\Temp\EFMigrationTemp—you can even make a quick PowerShell script to do this in one click if you do this often.

2. Generate Migration Scripts Programmatically (No Package Manager Console Needed) #

If you want to skip the Package Manager Console entirely, you can use EF’s migration API directly to generate the SQL script without creating any files in your solution. This is my preferred approach because it’s fully controllable and automated.

Create a small helper console app (or add a method to your existing project that you can run once) with this code:

using System.Data.Entity.Migrations;
using System.IO;
using YourProjectNamespace; // Replace with your DbContext's namespace

public class EfScriptGenerator
{
    static void Main(string[] args)
    {
        // Use your existing EF Migration Configuration class
        var migrationConfig = new Configuration();
        var migrator = new DbMigrator(migrationConfig);
        var scriptor = new MigratorScriptingDecorator(migrator);

        // Generate the full script from the initial state to your current model
        string migrationScript = scriptor.ScriptUpdate(sourceMigration: null, targetMigration: null);

        // Save to a temp file or copy directly to your clipboard
        string tempScriptPath = @"C:\Temp\LatestDbMigration.sql";
        File.WriteAllText(tempScriptPath, migrationScript);
        
        // Optional: Copy to clipboard for quick pasting into your DbUp file
        System.Windows.Forms.Clipboard.SetText(migrationScript);
        Console.WriteLine("Migration script generated and copied to clipboard!");
    }
}

• Run this helper whenever you update your EF model—it’ll spit out the complete SQL script (including the __MigrationHistory entry) without touching your solution files.
• You can even tweak this to generate only the delta from the last applied migration if you track the migration ID manually, but the full script works great if your DbUp scripts are run in order.

3. Bonus: Keep DbUp and EF in Sync #

Since you’re including the __MigrationHistory insert in your DbUp scripts, EF will recognize that migrations have been applied when your app runs—so you don’t have to worry about EF trying to apply migrations on startup. Just make sure your DbContext initialization is set to avoid automatic migrations:

public class YourDbContext : DbContext
{
    public YourDbContext() : base("YourConnectionString")
    {
        Database.SetInitializer<YourDbContext>(null); // Disable automatic migrations
    }
}

Best Practices to Make This Smooth #

• Number your DbUp scripts: Use sequential prefixes (like 0001_, 0002_) so DbUp runs them in the correct order every time.
• Test scripts first: Always run the generated SQL against a local test database before adding it to your DbUp collection—catch issues early!
• Automate in CI/CD: If you’re using a pipeline, integrate the programmatic script generation into your build process to generate the migration script when your model changes, then commit it to your repo automatically.

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