Generic repository pattern with unit of work in asp.net core web api

preview_player
Показать описание
Learn how to implement the Generic Repository Pattern with Unit of Work in ASP.NET Core Web API for CRUD operations. In this tutorial, we'll explore the fundamentals of repository patterns, the advantages of using a generic repository, and how to integrate it seamlessly with the Unit of Work pattern.

web api
generic repository pattern
unit of work
CRUD operation
repository pattern tutorial
web development
coding tutorial
software architecture
generic repository pattern and unit of work c#
generic repository pattern unit of work dapper
generic repository pattern with unit of work c# net core
generic repository pattern c# unit of work .net 6
generic repository pattern c# unit of work dapper
what is unit of work in repository pattern
repository pattern vs generic repository
unit of work pattern c#
unit of work pattern c# .net core 6
unit of work pattern java
unit of work pattern salesforce
unit of work pattern python
unit of work pattern apex
unit of work pattern c# github
unit of work pattern c# interview questions
unit of work pattern c# .net core
unit of work pattern c# .net core dapper
what is unit of work in .net core
unit of work pattern c# example
unit of work pattern with generic repository
how to implement unit of work pattern with dapper
what is unit of work pattern
when to use unit of work pattern
unit of work pattern nedir
what is unit of work design pattern
how to implement unit of work
how to use unit of work in c#
how to create unit of work in c#
is unit of work necessary
how to implement standard work
why use unit of work
what is the unit of work
why unit of work and energy are same
why unit of work pattern c#
why unit of work
why the unit of work is joule
why units are important
why is it important to use units
unit of work and generic repository pattern
generic repository and unit of work pattern .net core

#aspnetcore #webapi #repositorypattern #UnitOfWork #crudoperations #codingtutorial #webdevelopment #dotnetcore #programmingtips #softwarearchitecture
Рекомендации по теме
Комментарии
Автор

What's the preferred method of using "SaveChanges"? I noticed you left "SaveChanges" in Generic Repo but you also added it to the UOW implementation. Are you counting on the transaction to handle or undo any unwanted "Saves" when using the UOW but leaving the possibility to use a Repository outside the UOW and still have access to "SaveChanges" in connection with an add or update?

Also, wold you attempt to explain the differences to a development team or just pick one "Save" implementation or the other?

Thank you for contributing your time and efforts to the development community!

williamatkinson
Автор

EF does keep a transaction automatically, if it's in the same save changes in the same database... are you sure we need a begin/end transaction in UOW?

dmzone
Автор

Hi, I don't see any link in the description of this video for any GitHub link for the source code. Can you please put a link in the video description for the same? It would help me study the bigger picture. Thanks.

BabuKuvakkattayil
Автор

can you share the migration command it is shows More than one DbContext was found.

jayakumar
Автор

A whole load of code for no good reason.

fifty-plus