DEV Community

Discussion on: Dapper.NET: Handling Multiple Resultsets

View post

Replies for: Hi Dapper is surely faster (you can check the performances here: github.com/StackExchange/Dapper#pe...) but is not necessarely better than EF Core....

Collapse
 
shaijut profile image
Shaiju T • • Edited

Thanks, What are the reasons to prefer Dapper.NET over ADO.NET ? I think ADO.NET should be more faster than Dapper.NET and Entity Framework.

Also I don't like to see SQL select statements inside Application code. So I create ADO.NET repository with Stored Procedures for SELECT. I think it's more clean and maintainable.

Thread Thread
 
yorek profile image
Davide Mauri •

Dapper.NET extends ADO.NET. Great, you're following the best practices already, by separating SQL code from .NET code and using Stored Procedures.