Hello there. We noticed after doing this even though it worked to create the initial migration and update the database correctly, when we run add-migration to create a new one with changes we're doing to the model, the new migration gets created with all of the same structures that the initial migration already created causing duplication errors. Any ideas why it's not doing the "diff" to create only the new changes?
Also had to change MyCompanyName\src\MyCompanyName.Core\Authorization\Users\UserRegistrationManager.cs in order to comment out CheckForTenant call in RegisterAsync and all tenant-dependent logic in there.
Ok, I'm using the Angular template, but think I found what I needed in MyCompanyName\src\MyCompanyName.Web.Host\src\account\login\login.component.html by negating multiTenancySideIsTeanant in the associated areas. Gonna check out if the whole flow works ok.
That is already the case, but when I enable any of the social logins such as Microsoft, it only shows the buttons for login at the tenant level. I understand that setting controls whether or not the tenant has access to configuring additional social logins, etc.
What I'm looking for is to use those social login settings I defined in appsettings.json but in the Host login.
Ok, I missed one important piece of information from the instructions:
Remove all migration classes (including DbContextModelSnapshot) under *.EntityFrameworkCore/Migrations folder;
Ok, just did and the migration that gets created isn't a valid one. It starts with dropping FK constraints that dont even exist since the db is empty:
