this concept is discussed here <a class="postlink" href="http://benfoster.io/blog/asp-net-core-dependency-injection-multi-tenant">http://benfoster.io/blog/asp-net-core-d ... lti-tenant</a>
"f a singleton is created once per application, you can probably guess that a tenant-singleton is created once per tenant.
So when might you need this scope? Think of any object that is expensive to create or needs to maintain state yet should be isolated for each tenant."
Any ideas/example here on extending existing ABP tables?
Found out that you need to use per project
: AbpModule { public override void Initialize() { IocManager.RegisterAssemblyByConvention(Assembly.GetExecutingAssembly()); }
any idea?
i was able to GUESS what my problem was , but ABP should be able to throw those exception above. it was in DI layer i think. because i had my class defined as
public partial class PersonDataRepository : , IPersonDataRepository
{
}
public interface IPersonDataRepositoryExtended : IPersonDataRepository
{
}
public partial class PersonDataRepository : IPersonDataRepositoryExtended, ISingletonDependency
{
}
and i had depndency on IPersonDataRepositoryExtended