Enabling multi-tenancy in a new Blazor WASM project results in the following error in server\Controllers\AccountController.cs:
A local or parameter named 'user' cannot be declared in this scope because that name is used in an enclosing local scope to define a local or parameter
Adding multi-tenancy to a simple Northwinds test project, gives the following error in client\Pages\AddApplicationRole.razor.designer.cs:
Argument 1: cannot convert from 'Microsoft.AspNetCore.Identity.IdentityRole' to 'RadzenTestWa.Models.ApplicationRole'
You can check it when switching between security with/without multi-tenancy - will be unchecked by default to keep the current behavior to not overwrite already added security pages.