无法创建迁移为现有表新增列：提示“无效列名”错误

Hey there, let's work through this frustrating migration issue you're facing! Even though you're just adding a straightforward string column with no constraints, the error about an invalid [column id] and failing to create DashboardContext suggests EF is hitting a mismatch between your entity model and database during the migration creation process. Here are the most likely fixes:

1. Check for Pending Migrations & Sync Your Database #

First off, it's possible you have old migrations that never got applied to your database, leaving the schema out of sync with your entity model.

• Run this PowerShell command to see all migrations and their status:

  Get-Migrations -Context DashboardContext
  

• Compare the list with the entries in your database's __EFMigrationsHistory table. If there are pending migrations, apply them first:

  Update-Database -Context DashboardContext
  

Once your database is fully synced with existing migrations, try creating your new migration again.

2. Fix Context Initialization Logic That Hits the Database #

EF needs to spin up your DashboardContext to generate migrations, and if your app's startup logic (like in Program.cs or Startup.cs) tries to query the database during initialization, it'll fail if the schema doesn't match.

• Open your Program.cs and adjust the BuildWebHost method to skip database-dependent logic when migrations are being created. For example:

  public static IWebHost BuildWebHost(string[] args)
  {
      var isMigrating = args.Any(arg => arg.IndexOf("migrations", StringComparison.OrdinalIgnoreCase) >= 0);
      
      return WebHost.CreateDefaultBuilder(args)
          .ConfigureServices(services =>
          {
              // Only initialize services that access the database if we're not running migrations
              if (!isMigrating)
              {
                  // Add your database-dependent service setup here
              }
          })
          .UseStartup<Startup>()
          .Build();
  }
  

This prevents EF from trying to run database queries while it's trying to generate the migration itself.

3. Verify Entity Model & Database Schema Match #

Double-check that your entity model doesn't have a property mapped to the missing [column id] column that doesn't exist in your database.

• Search your entity classes for a property that might map to this column (look for [Column("[column id]")] attributes or convention-based names).
• If you find such a property, either:
  • Manually add the missing column to your database (if it was supposed to be there), or
  • Roll back to a migration where the schema matched and reapply migrations correctly (avoid manual database edits in the future if you're using Code First!).

4. Ensure You're Using the Correct Context & Connection String #

Sometimes the issue is just targeting the wrong database or context:

• Explicitly specify your context when running the migration command to avoid ambiguity:

  Add-Migration AddNewStringColumn -Context DashboardContext
  

• Confirm your appsettings.json (or environment-specific config) has the correct connection string pointing to the database you intend to use. You can also set the environment in PowerShell first:

  $env:ASPNETCORE_ENVIRONMENT = "Development"
  

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