Repository pattern with EF Core in an ASP.NET Core API

preview_player
Показать описание
In this video we show the basic building blocks to implement the repository pattern in an ASP.NET Core API using, of course, EF Core.

Join this channel to get access to perks:

Рекомендации по теме
Комментарии
Автор

Excellent intro to repository patten with EF Core!

anonymoos
Автор

This is one of the easiest to understand videos I've watched on c#

markodigie
Автор

What you said about not worrying too much about whether to use the repository pattern or not was really helpful!

jayeshsingh
Автор

Simply said and nicely presented. Good work!

konstantinosantoniou
Автор

Explanation was awesome, thanks for all the useful information. I was in a little bit confusion about repository pattern by this video it made me easy to understand tq so much

sampathchaganty
Автор

Thanks, this video was of great help.

vajrabhagwat
Автор

Good information, I like the way you presented.

nirajjoshi
Автор

You are great. Thank you for your video. Broken down to an understandable level with a lot of additional information.

TauwinKul
Автор

How did you get intellisense so show the namespaces when you typed "IBookRepository" in 6:45?

zerosandones
Автор

Your controllers and repositories are all directly dependent upon EF. Now try testing without a database; you need to rewrite all your repositories as test repositories. Also what you wrote is a data provider for EF. Repositories should be agnostic of persistence technology and may access various data providers. This is why repositories should be implemented in the business layers and not the DAL. Repositories should answer business queries, not simply wrap a specific ORM.

I would have included transactions as well, even for a getting started.

Cyrdian
Автор

Quick question about Clean Architecture. If my application doesn't share info with other apps - is there still a need for the Domain layer?

CarrigansGuitarClub
Автор

If youre gonna add Entity framework validation property such as minLength/maxLength, [required] etc. . Should we put it in the domain model/entity or putting it only in DTO is fine?

zedshockblade
Автор

I have a question: makes sense (and we must do that) the construtor of the repository receives as a parameter an interface of the AppDbContext instead oh the concrete class? Or this wouldn't work? I'm asking it regarding to keep the code loosely coupled and all the good and recommended practices! Thanks, greetings from Portugal.

solracepilif
Автор

How can i get a list of users based on parameter? For example i can get a list of users where category = 5. Can you help me? Sorry for bad english, i am Braziliam

Jabrelz
Автор

5:26 - the North Vietnamese Army doesn't approve 😂😂😂

RoboTHUG
Автор

It’s said that your not ment to use repository with ef core

dotnetdevni
Автор

Thanks for sharing. Please make a video tutorial repository where Entities, Dtos, ViewModels existing in different projects (class library).

ShakirAlimit
Автор

What is the difference between Services and Repositories?

Our file structure is like

- / Services
---/ IBookService
---/ BookService

donmikkodanm.olmillo
Автор

how can be divide into multiple layer like Database Business layer and service layer with ui please if you have any idea

Narendra
join shbcf.ru