Finbuckle.MultiTenant is an open-source multitenancy middleware library for .NET. It enables tenant resolution, per-tenant app behavior, and per-tenant data isolation.
I'm having this problem now and it is surely a configuration problem. But the generic message isn't helpful pointing to where the problem is.
It seems several other issues (#799, #465, #340, #140) had the same problem.
More informative messages like
No tenant with id = "ACME" was found in the configured stores.
No MultiTenant Strategy registered. Please see https://www.finbuckle.com/MultiTenant/Docs/ConfigurationAndUsage
No MultiTenant Store registered. Please see https://www.finbuckle.com/MultiTenant/Docs/ConfigurationAndUsage
and others would surely help.
This way, if we see the generic Unable to resolve service for type ... message again we could probable use this as a good indicator for "You forgot to call .Add/UseMultitenant()."
I like this idea. One reason I removed DI for TenantInfo was to eliminate one major cause of these exceptions and these errors messages would go further.
I'm having this problem now and it is surely a configuration problem. But the generic message isn't helpful pointing to where the problem is.
It seems several other issues (#799, #465, #340, #140) had the same problem.
More informative messages like
No tenant with id = "ACME" was found in the configured stores.
No MultiTenant Strategy registered. Please see https://www.finbuckle.com/MultiTenant/Docs/ConfigurationAndUsage
No MultiTenant Store registered. Please see https://www.finbuckle.com/MultiTenant/Docs/ConfigurationAndUsage
and others would surely help.This way, if we see the generic
Unable to resolve service for type ...
message again we could probable use this as a good indicator for "You forgot to call.Add/UseMultitenant()
."Also: #628 (related).