ASP.Net Core Web Api CRUD with Dapper and Repository Pattern

  • 🎬 Video
  • ℹ️ Description
preview_player
UCNwFQFVL0RSHLsM7rAOf_hg


💬 Comments
Author

Thank you very much, a super like from Brazil!!

Author — José Eduardo

Author

great man. I true appreciate your effort.
unfortunately, its not fully completed. waiting for the next video with rest parts.

Author — Imon Islam

Author

Please add the Swagger testing of what has been developed and a bit more of an explanation, great tut!

Author — Kennedy Lekoko

Author

Hi Alex,
Can i use dapper of Postgressql, does the code in your repo works for postgres?

Author — Nambi Ramamoorthy

Author

It it possible to dot it without MediatR & CQRS? Glad to hear from you.

Author — Imon Islam

Author

Hello, the video stops after editing appsettings.json, whats next?

Author — Jorge Blanco

Author

I do not understand your implementation of UnitOfWork. Isn't it usually used to surround multiple database operations in a transaction?

Author — Gerd Bauersfeld

Author

Maybe use a different class name other than 'Task' haha but great tutorial!

Author — Samuel Zrna

Author

Great video, but can you finish the video please??

like from Brazil!

Author — Gabriel P. Maricato

Author

I'm getting a 405 error. Can you help me?

Author — Faruk Seyhan

Author

Good video and very informative, but the mouse clicking has to go... To annoying.

Author — The Gem Garden

Author

perfect! easy to understand. Thanks mate, cheers!

Author — Junaid Ahad

Author

Was good until i found out if was INCOMPLETE!!! :/, missing the WHOLE closure (adding all of this to the controller)

Author — Rodrigo

Author

The complete code is on his blog at the link above. Good tutorial, bad video.

Author — jdtracy

Author

Wouldnt it be better to have Task repository inherit Generic Repository so you dont have to write implementation in every repo ? In this case GenericRepository has to look different, it should only contain truly generic methods like Query, QuerySingle etc and leave the specific add/update implementation details to be implemented by every individual repo itself

Author — Ihor Bodnarchuk

Author

Your unit of work not doing its actual work. it just only wrapping your repositories. Unit of work is used to manage and control the SQL transactions.

Author — rishad ali

Author

You're not explaining what you are doing. Just typing and voice over.
And also what makes it more confusing is the example entity named "Task" which has a specific meaning in C#.

Author — Saad Malaeb