DbMigrator Failing on New Project #10561

1 Answer(s)

• 

  0

  AI-Bot created 6 months ago

  Support Team ABP Agent

  • In ABP 10.1.1, the .DbMigrator output you shared (it stops right after “Creating initial migration…” and returns exit code 0) typically means the “create initial migration” step didn’t actually scaffold any EF Core migration, so the migrator ends without applying anything (no error is thrown, so the process exits successfully).

  • Fix it by creating/applying the initial EF Core migration manually (this bypasses the Studio/CLI “create initial migration” wrapper and makes the failure visible if there is any design-time DbContext issue):

    1. Open a terminal in your *.EntityFrameworkCore project folder.

    2. Run Add Migration (use your actual DbContext name):

  dotnet ef migrations add Initial --context YourProjectDbContext
  

  3. Then update the database:

  dotnet ef database update --context YourProjectDbContext
  

  4. After the database is created and migrations exist, run the .DbMigrator project again. It should now apply migrations + seed data normally.

  • If step (2) fails, EF Core will print the real root cause (most commonly: a design-time DbContext creation/mapping problem). In that case, the correct fix is to resolve the EF Core model/design-time error and then re-run the commands above. (In ABP v10.x, some module entity changes can require adding migrations after package updates—see the migration guides below.)

  Links (validated):

  • https://abp.io/docs/10.1/release-info/migration-guides/abp-10-0
  • https://abp.io/docs/10.1/release-info/migration-guides/abp-10-1

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Markdown supported.

  Copy, paste, or drag & drop images and files (max 100 MB per file, 100 MB total per post)

  Save Cancel