Activities of "cstobler"

I just upgraded to Pro and also just upgraded to .NET 9. I went to run my Web project and ran into this: I had updated that line based on this documentation: https://abp.io/docs/latest/release-info/migration-guides/abp-9-0. The intellisense shows it as a nullable argument, so I'm not sure why it is throwing this error.

If you need to see my project, I uploaded it for another ticket (9542) via email.

Thanks in advance for any help you can provide,

Charlie

Not sure of ABP version (can't find solution configuration in ABP Studio (along with other features documentation says I am supposed to have, could be related to other issues below)

• Exception message and full stack trace:
  • Exception thrown: Microsoft.Data.SqlClient.SqlException: 'Invalid object name 'SaasTenants'. This exception was originally thrown at this call stack: [External Code] Armada.Data.ArmadaDbMigrationService.MigrateAsync() in ArmadaDbMigrationService.cs
  • This threw an exception directly on the line "var tenants = await _tenantRepository.GetListAsync(includeDetails: true);" and stopped execution.
• Steps to reproduce the issue:
  • Set DbMigrator as startup project
  • Run DbMigrator
  • Get stopped with error above
• Explanation:
  • I think something might have gone wrong when I went to migrate my project from open source to pro. First, I wasn't able to find the "Upgrade to Pro" button in ABP Studio, so I just called "abp upgrade -t app". This threw some errors and warnings in the console, but when I checked, it appeared that the changes were made to the project. However, I think some things weren't executed properly in the upgrade.
  • First, there were a lot of errors, most of which were because it installed the 4.2.1 version of LeptonX, but all of the other modules were on v8.x.x, which seemed to be causing issues. I then went into NuGet for each project and updated all of the Volo packages to v9.2.1, and that seemed to resolve those errors. I also resolved various errors that were expected (breaking changes due to the ABP upgrade or .NET upgrade).
  • With all of the errors resolved, I went to run my DbMigrator to make sure that the database was up-to-date, at which point I was presented with the error above. I checked my migrations directory and found that there were no new migrations present, and when I checked my tables in SSMS, there were no Saas tables as I was expecting to see. I do believe my DbContext.cs is configured correctly. I did have to make a few adjustments based on this article: https://abp.io/docs/commercial/latest/migrating-from-open-source?DB=EF (which further leads me to believe that something went wrong in the upgrade), but DbContext does contain everything that article lists except builder.ConfigureOpenIddictPro(), which is shown as not existing, so I have defaulted to builder.ConfigureOpenIddict() (probably separate issue but also concerning).
  • At this point, I'm not sure what to do. I tried upgrading the project again, but that doesn't do anything. I know I need those Saas tables in the database, but I don't know how to force a migration since the migration doesn't even exist under Migrations and trying to run DbMigrator just returns the above error.
  • Please let me know what additional information you need to help troubleshoot this. Any help would be greatly appreciated!

Charlie