You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to write about a small issue that is concerned for every new comer in backend development with ASP.NET Core, using ORM EntityFramework Core, That they should implement the Unit of Work & Repositories patterns. Which is complete non sense - to some extent - from my point of view.
Goals
Learn why it is not best practice.
How to make it better.
Finally how to really extend this to it's maximum power.
Outline
What is EntityFramework Core?
What is Unit of Work & Repositories Design Patterns?
Why isn't it logical to apply them to EntityFramework Core?
How to apply them correctly?
Sample articles
N/A , But you can check my github for complete in-depth documentation of my libraries/projects!
The text was updated successfully, but these errors were encountered:
Introduction
I would like to write about a small issue that is concerned for every new comer in backend development with ASP.NET Core, using ORM EntityFramework Core, That they should implement the Unit of Work & Repositories patterns. Which is complete non sense - to some extent - from my point of view.
Goals
Learn why it is not best practice.
How to make it better.
Finally how to really extend this to it's maximum power.
Outline
Sample articles
N/A , But you can check my github for complete in-depth documentation of my libraries/projects!
The text was updated successfully, but these errors were encountered: