Andrew White

Hi, two main reasons. 1) dependency injection: it needs to work with DI and injecting a string type wasn’t feasible until keyed services very recently 2) users may want to...

Hi again, `DbContextOptions` and its builder don't really follow the normal options pattern and when used with `AddDbContext` it isn't obvious how/if per-tenant options can be applied -- so in...

You are correct but I have a PR coming soon that changes this. Soon only `IMultiTenantContextAccessor` will be available straight from DI. I’m doing this to more closely match how...

I agree with yo that it is a best practice. There are some use cases where some entities make sense to not be multi tenant but part of the overall...

Also it’s on my list to look at using interceptors for the functionality or maybe events. Neither were an option back when I started. That would make it easier to...

Yep, here is the section: https://www.finbuckle.com/MultiTenant/Docs/v6.13.1/EFCore#adding-multitenant-functionality-to-an-existing-dbcontext

Hi, you just define your own `ITenantInfo` that has a connection string property and use that. Nothing else really needed.

Hi, sounds like you want the idea of a “sub-tenant”. The library doesn’t have any built in support for this and it’s a somewhat advanced use case. I recommend building...

The library is agnostic to the Identity Entity models except that it was add and check for the tenant id as configured. If you want to add more properties and...

One idea is to register a "dummy" interface in DI which uses a lambda to instantiate your dbcontext with a constructor of your choice, i.e. one that isn't dependent on...