Activities of "cstobler"

Thank you for the clarification. I ended up making a new database anyway since it was on master, but the thing that ended up working for me was to also delete the DbContextModelSnapshot.cs file, which then allowed the migration file to fill properly and that fixed the database issue as far as I can tell.

I am having another issue, but I think it is best suited to another ticket. Thanks again for your help!

Thanks for looking into this. I deleted all of the migrations, created a new one using the CLI, and the new migration was again empty: I'm not sure what is going on here. I can delete the databases if necessary, like I said, there is no permanent data on there that needs to persist. But I'm not sure how to go about this in a way that will result in a clean slate. I checked your documentation and the book, and they both say to just run DbMigrator to create a new database, which worked for me in the beginning but obviously isn't working now.

Charlie

I zipped up my solution folder and sent it via email with the ticket number.

Additionally, not sure the best way to show this, but here are my tables so you can see that it doesn't have SaasTenants, or the other tables I was expecting:

My database is still being used for testing and can easily be recreated, so if we need to recreate it, that is totally fine.

Charlie

I still need help. To provide some additional information based on the AI agent's suggestions:

• I have typeof(SaasEntityFrameworkCoreModule) rather than typeof(AbpSaasEntityFrameworkCoreModule). I'm not sure what the difference here is or if I need to use the other one. It does look like it recognizes what I have there already. Advice would be appreciated.
• builder.ConfigureSaas() is present in my DbContext.cs under OnModelCreating(). Weirdly, there were 3 identical builder.ConfigureSaas() lines, which additionally makes me think that something went wrong. Note that I removed these before trying, so that wasn't directly causing the problem.
• When I use "dotnet ef migrations add" to create a new migration, it just creates an empty migration. Technically I added Volo.Abp.LanguageManagement.EntityFrameworkCore from the article above, which then added things to my migration, but nothing related to the Saas tables that I need.