Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *


  1. Hi mukesh
    Thank you for Great Articles
    Recently i find your weblog and i think most of them are excellent so i start to study all of them

    when your last project (ASP.NET Core Hero – Boilerplate Template) will be completed?? and why you dont use blazor-webassembly instead of razor pages for UI?

    than you again

    1. Hi Sadi,
      Thanks for your feedback.

      I have moved the entire codebase of my newest project – ASP.NET Core Hero 5.0 to . And yes, I have moved away from Razor Pages to MVC. About Blazor, it will be added as a Client Application later on in the roadmap. For now, I am working to complete the API + MVC Boilerplate. Do give it a look. The basics are almost taken care of.


  2. Hi Mukesh,
    Thank you for the article, very useful as usual..
    As an opinion, it will be interesting an article about using net core with winforms (desktop app) and integrating it with clean architecture, EF, dependency injection, validating, CQRS (and don’t know if is aplicable in a winforms app), etc.
    Thanks a lot and best regards.

  3. Hi brother,excellent work.

    I am just learning and sorry if it is very basic question . I tried to integrate this dapper EF mix to your boiler plate, but I am lost, :).. I guess then the connection to be mentioned in the application layer each query handler. Any thought?

    Thank you

  4. Hi Mukesh, thanks for this article, it’s very good and useful. Do you have any other using stored procedures instead of query?

  5. “Dapper is literally much faster than Entity Framework Core”
    no, it isn’t 🙂 (and this test didn’t even used AsNoTracking in the select case)

    Dapper can be much faster in case of complexes queries because EF can create some strange query path, but on general, no, Dapper isn’t that much faster than EF if you know how to use it properly (ie: use AsNoTracking for select)

    just my 2 cents 🙂

    1. Thank you. I couldn’t even read the rest of the article since it started with this sentence.

      It shows a lack of in depth understanding of how to use the technologies. EF provides a lot more options, but can be just as fast if you strip it down to the basics and configure it properly.

      Dapper is literally much faster than Entity Framework Core considering the fact that there are no bells and whistles in Dapper. It is a straight forward Micro ORM that has minimal features as well. It is always up to the developer to choose between these 2 Awesome Data Access Technologies. This does not mean that Entity Framework Core is any slower.

      “Dapper is literally much faster than Entity Framework Core” LITERALLY MEANS that Entity Framework Core is slower.

  6. Hi Mukesh,

    Thanks for the detailed article. I have been trying to extend it with UnitOfWork pattern along with Generic repository pattern. While doing the implementation I came across few issues which is available at :

    I am trying to leverage Dapper for readonly operations and EntityFrameworkCore for Create, Update, Delete operations.

    Any help on this request is much appreciated


  7. Hi Mukesh,

    It would be very much helpful if you extend this article in terms of UnitOfWork, GenericRepository , CQRS, Mediatr patterns. It is something like complete Clean Architecture with Dapper including all the patterns included in it.

    Thanks again for all your great articles


  8. This helped me resolve an issue where I was missing `_dbContext.Database.UseTransaction(transaction as DbTransaction);`. Thank you!

  9. I looked into the code and it looks like that Dispose would never be called for ApplicationReadDbConnection. Is it true?

  10. I looked into the code and it looks like that Dispose would never be called for ApplicationReadDbConnection. Is it true? Implementing finalizer might help in this case.