DbSet is your repository and DbContext is your UoW, you don't need to wrap a repository in a repository. It is much simpler and cleaner to create a service layer that consumes the DbContext/s.
Nice and simple explanation. Waiting for the unit of work implementation and explanation about how UoW works. I request to u that, If u can create Service layer which will directly injected in the controller like IProductService, IOrderService, IBlogService.
DbSet is your repository and DbContext is your UoW, you don't need to wrap a repository in a repository. It is much simpler and cleaner to create a service layer that consumes the DbContext/s.
This session I tried to cover only uow with generic repository in upcoming session I will use it in clean architecture which is already in my chanel
Nice and simple explanation. Waiting for the unit of work implementation and explanation about how UoW works. I request to u that, If u can create Service layer which will directly injected in the controller like IProductService, IOrderService, IBlogService.
Sure, in my chanel I already cover service layer you can check out even I create complete session of clean architecture you can refer that.
You already have Unit of Work and it's called Entity Framework DbContext.
Awesome brother, I like to way of teaching, bother do one thing please share the code in the description
Thanks github.com/kartik786-git
Great video, can you please share the project with us?
Please check out my github link with same solution name
CRUD and real world are two opposite things
This sample we can used in our real project easily. In upcoming session I will use in our clean architecture