- ABP Framework version: v7.4.2
- UI Type: Blazor WASM
- Database System: EF Core (SQL Server)
- Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
- Exception message and full stack trace:
- Steps to reproduce the issue:
Hi,
I have the same isssue as https://support.abp.io/QA/Questions/2745/How-to-add-Dapper-to-existing-porject. How did you solve it?
Thanks.
4 Réponse (s)
-
0
Hi,
You can check the unit tests: https://github.com/abpframework/abp/blob/dev/framework/test/Volo.Abp.Dapper.Tests/Volo/Abp/Dapper/Repositories/PersonDapperRepository_Tests.cs#L14
-
0
Hi,
The tests don't show how you resolved the issue. Allow me to remind you that the problem was that the implementation of the Dapper interface wasn't properly descoved by dependency injection. I succeeded to resolve the issue by mannually register the interface and implementation. I've just wondering how you have solved the issue.
Cheers, Yulian
-
0
Hi,
This may be a naming convention issue,
When one implements multiple interfaces, ABP doesn't know which one to register, So ABP uses the naming convention.
For example:
public interface IDapperBookRepository { } public class DapperBookRepository: DapperRepository<xxx>, IDapperBookRepository, ITransientDependency { } -
0
Ok. I've understood.
