the patch release 4.4.1 will be released next week. @maliming is this issue fixed in the 4.4 branch?
see my Gist https://gist.github.com/ebicoglu/543928d2dec68ce4fc0ddf25b8e39bac
this error looks like specific to you. did you change the this file manually
%UserProfile%\.abp\suite\appsettings.json
if yes, rename it to appsetting.backup.json and try to add your solution again.
closing this ticket. will be fixed in the next release if you encounter the same problem you can reopen this.
the hacky way is disabling IMultiTenant data filter to access data btw different tenants. see https://docs.abp.io/en/abp/4.4/Data-Filtering#imultitenant
but this is possible if all your tenants share the same DB.
if you change the tenant explained in the following doc, ABP Framework will set the TenantId https://docs.abp.io/en/abp/4.4/Multi-Tenancy#change-the-current-tenant
there's only 1 test in the saas application test project and it's a sample test without any test inside.
what's the exception?
ConfigureIdentityServer() method.check out the following document for this scenario: https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Migrations#using-multiple-databases
seems like a problem related to Visual Studio.
this package doesn't belong to the ABP Microsoft.VisualStudio.TestPlatform.Fakes
try to run tests via command line
this is not possible in ABP!
if you need such a requirement, it means you are on the wrong path. reconsider why you need a user to be logged in tenants. alternatively, you can create the same user with the same credentials in each tenant. but the architectural design doesn't allow sharing data between tenants, because each tenant must be considered as a different instance (setup) of your application.
The following docs will help you
