ASP.Net Core 2中Update-Database创建数据库失败问题排查

Hey there! Let's tackle your ASP.NET Core Web API issues one by one, starting with the migration error, then code checks, and finally VS Code debugging.

1. Fixing the Update-Database Error (AspNetRoles Already Exists) #

First off, your understanding of migration commands is mostly correct:

• Add-Migration generates code to track schema changes for your database.
• Update-Database applies those changes to create the database and tables.

The error happens because your target database already has the AspNetRoles table (and likely other Identity tables) either:

• You manually created them earlier, or
• A previous migration was applied but not properly tracked in EF's migration history table (__EFMigrationsHistory).

Solutions: #

Option 1: Start fresh (if no existing data to keep)

• Delete the entire database from SQL Server (or your DB provider).
• Re-run the migration commands in order:
  1. In Package Manager Console (PMC):

     Add-Migration InitialCreate
     Update-Database
     

  2. If using .NET CLI (works in VS Code too):

     dotnet ef migrations add InitialCreate
     dotnet ef database update
     

     Note: If you don't have EF tools installed globally, run dotnet tool install --global dotnet-ef first.

Option 2: Keep existing database (if you have data you can't lose)

• First, check which migrations have already been applied:

  Get-Migrations
  

• If the Identity tables already exist but aren't tracked in migrations, create an empty initial migration to sync EF's history with the current database state:

  Add-Migration InitialCreate -IgnoreChanges
  Update-Database
  

  This tells EF that the current schema is the baseline, so future migrations will only track changes from this point onward.

2. Checking Your Code for Potential Issues #

Based on the files you mentioned (Program.cs, Startup.cs, ApplicationDbContext.cs), here are common pitfalls to look for:

ApplicationDbContext.cs #

Ensure you're inheriting from IdentityDbContext (not just DbContext) to let EF handle Identity tables correctly:

using Microsoft.AspNetCore.Identity.EntityFrameworkCore;
using Microsoft.EntityFrameworkCore;

public class ApplicationDbContext : IdentityDbContext<IdentityUser>
{
    public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
        : base(options)
    {
    }

    // Add your custom DbSets here if needed
}

If you're using a custom user class (e.g., ApplicationUser), replace IdentityUser with that class.

Startup.cs (or Program.cs for .NET 6+) #

For .NET 5 and earlier (Startup.cs):

Make sure you've configured the DbContext and Identity services properly in ConfigureServices:

using Microsoft.AspNetCore.Identity;
using Microsoft.EntityFrameworkCore;

public void ConfigureServices(IServiceCollection services)
{
    // Configure DbContext with your connection string
    services.AddDbContext<ApplicationDbContext>(options =>
        options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection")));

    // Add Identity services
    services.AddDefaultIdentity<IdentityUser>()
        .AddEntityFrameworkStores<ApplicationDbContext>();

    // Add Web API services
    services.AddControllers();
}

For .NET 6+ (Program.cs):

The configuration is similar but uses the top-level statements:

var builder = WebApplication.CreateBuilder(args);

// Add DbContext
builder.Services.AddDbContext<ApplicationDbContext>(options =>
    options.UseSqlServer(builder.Configuration.GetConnectionString("DefaultConnection")));

// Add Identity
builder.Services.AddDefaultIdentity<IdentityUser>()
    .AddEntityFrameworkStores<ApplicationDbContext>();

// Add controllers
builder.Services.AddControllers();

var app = builder.Build();

// Middleware configuration (omitted for brevity)
app.UseAuthorization();
app.MapControllers();
app.Run();

Connection String #

Double-check your appsettings.json has a valid connection string pointing to your SQL Server instance:

{
  "ConnectionStrings": {
    "DefaultConnection": "Server=(localdb)\\mssqllocaldb;Database=YourWebApiDb;Trusted_Connection=True;MultipleActiveResultSets=true"
  }
}

3. Debugging ASP.NET Core in VS Code #

Here's a quick setup to debug your app in VS Code:

1. Install the C# extension from the VS Code Marketplace (Microsoft's official one).
2. Open your project root folder in VS Code.
3. Press F5 – VS Code will prompt you to generate a launch.json file (if it doesn't exist already).
4. The default launch.json should work for most cases, but verify the program path points to your compiled DLL (e.g., ${workspaceFolder}/bin/Debug/net6.0/YourProjectName.dll).
5. Set breakpoints in your code (click the gutter next to the line number), then press F5 again to start debugging. You can use the debug toolbar to step through code, inspect variables, etc.

内容的提问来源于stack exchange，提问作者Ahmer Ali Ahsan