Custom repositories should override the default repositories

We can create custom repositories easily. But even we create custom repository for a Person entitiy, we can still inject IRepository<Person>. That’s very good. But think that we overrided Delete method on the custom repository and changed delete logic a bit. What happens if we still use IRepository<Person> instead of custom IPersonRepository? Delete method will work as before. So, there will be 2 different Delete method implementations for same entity. This is dangerous!

So, while registering default repositories, we can check if there is a custom implementation and register IRepository<TEntity> as the custom repository.

[hikalkan]

This can be done manually using Configuration.ReplaceService (http://www.aspnetboilerplate.com/Pages/Documents/Startup-Configuration#replacing-built-in-services) in module’s PreInitialize, as shown bloe:

Configuration.ReplaceService<IRepository<Post, Guid>>(() =>
{
    IocManager.IocContainer.Register(
        Component.For<IRepository<Post, Guid>, IPostRepository, PostRepository>()
            .ImplementedBy<PostRepository>()
            .LifestyleTransient()
    );
});

I decided to not do it automatically, because we may have more than one dbcontext containing the same entity and we may have more than one custom repository implementation (for different dbcontextes) and ABP can not know which implementation to be used.

[acjh]

C# Generics: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/generics/index