🚀 Join the .NET Web Academy with a 30% discount - closing soon! 👉 www.dotnetwebacademy.com/courses/academy?coupon=dnwas23yt

I came here for the understanding of repository pattern but left with a full understanding of dependency injection. 😅 something I’ve been struggling to understand for weeks. Thanks man.

@PatrickGod

Жыл бұрын

Glad it was helpful! 😅

Came for a Repo Pattern explanation, stayed for the Dependency Injection explanation. I've watched several videos but it was yours that finally made it 'click' for me. Great example - not too abstract (as those "DI explained in n minutes videos) but also not too complex for beginners like me.

Thanks Patrick. I have been trying to learn this yesterday and this vid really clarified some points.I have been following several of you vids, Love the way you exlplain in such a peaceful way. Thanks Sir.

I like how this was explained without using EF, Dapper, etc... just focused on the design pattern. Very well explained!

Gut gemacht. Simple and very well put example. I always structure the code and pattern design like this. When you have too many services, be careful. Injecting services into each other in a circular manner can lead to runtime errors like stack overflow or infinite loops. It's best to avoid such circular dependencies and design your services in a more decoupled way to ensure proper functioning and maintainability. Otherwise, best way to go 👏🏼

I really like this pattern along with some more abstraction, in manner that we code a abstract class with generic parameter(class) with all data access functions, this could be reused for all entities around the application.

Thats actually not a Repository Pattern, that isolates the database connection but a service layer

@theonlycaulfield

10 ай бұрын

Yes, I am confused on how this is the top result for my query on ".net repository". A repository pattern separates the db connection from the logic in the service layer. This video represents the repository pattern as if it is the thing that the repository pattern is intended to prevent.

Point by point. Very well explained! Thanks a lot Man (Additional Subscriber)

explained in the best possible manner, thank you very much.

Good example, it also touches the basics of DI

Good work sir 👍 , on your next vlog please explain us how to work on multi tenant architecture with identity. for example: if the client is registering he will have master data base and, he will add some worker's below him they have their own separate database.

I am studying how to create multiple data acces classes to prevent having one enormous data acces class. I found the Service Pattern and Repository Pattern. I guess with creating an interface, you combine the two? Good video and nice combination of also showing the depency injection.

Thank you so much for this...I came to learn Repository Pattern but learned Dependency Injection..I wish I could tell you how much i struggled trying to grasp the concept of Dependency Injection..You have a new subscriber sir!!

@PatrickGod

10 ай бұрын

Wonderful! Thank you so much!

Great video! Kristina recommended your podcasts- I am on board!

Thank you, i know you just don't do the content for me (asked in a one of your videos about this) but many thank you I hope someday I can pay you back, right now I lost my job due to current environment so many thanks for the content.

Thanks Patrik, good example.

@PatrickGod

Жыл бұрын

Thanks Manuel, glad I could help!

Well explained brother. Got to learn more than expected.

Thank you very much!!!

Great Video. Thanks a lot!

Keep up, Patrick! You are a real God, man :D

@PatrickGod

Жыл бұрын

Wow, thank you so much! 😊

excellent explanation, thank You Patrick

Do you have any idea how to build multi-tenant architecture that has shared code base and a lot of database?

Many thanks!

@PatrickGod

Жыл бұрын

You're welcome!

Have you done the Factory Pattern? If not that would make for a great video as well

I have a question about registering the repository and service, if i have multiple interfaces and classes in a same folder, how can i register them quickly without having to write multiple builder.Services.AddScoped like this example: builder.Services.AddScoped() builder.Services.AddScoped() ... builder.Services.AddScoped()

Tks!

Sir, i have 1 question. What about dbcontext and dbset. For example: dbset User. Should i create a repository of user and inject that user db?

1. This looks exactly like your Udemy course I took a while ago. So I'm happy, that I'm already using it like this approach. 2. What game cardridge is inserted into your SNES? 😀

@PatrickGod

Жыл бұрын

1. Thank you so much for enrolling! 😊 2. The Legend of Zelda: A Link to the Past 🎮 Awesome you noticed!😁

You deserve more subscribers

@PatrickGod

Жыл бұрын

Thank you so much! I appreciate that. 😊

what is Full repository analysis in AWS site and what does it do? can someone explain pls....is this the place where i can find my app source code in AWS?

If have 50+ controllers and services should i need to inject every class(addscoped etc) into main class?

Unknowingly explained Dependency Injection too lol.

great. subscribed.

@PatrickGod

Жыл бұрын

Awesome! Thank you!

Thank you for explaining! One thing I would like to comment is that your controller in the example works just like a wrapper and adds no any functionality, so I think there is no really need to implement repository here.

thankyou

It is not a good explanation of Repository pattern. Repository pattern is for manipulating data as if it a collection. So any repository should have methods for adding, removing and getting data. Otherwise it is just data accessor service

Thanks for this. Never really understood what bit the 'repository' was... now you say it is pretty much the service (I use same term) it makes more sense. One question if I may. Working on my first app of this type (OpenAPI) and it seems you do have to register every single interface in program.cs (using .NET 7) which seems a lot of overhead to me?

Love from 🇮🇳 ❤

Say if I have multiple interfaces and classes to be registered in the Program.cs, is there any way that I can do it with a smarter way instead of registering them one by one?

@ofskiiboy

14 күн бұрын

You can use the Scrutor package which auto detects all your repo's and injects them

Good video, but what is a service exactly in this context? I've seen it used in a few places but I still don't know what it is referred to :/

Best

Hello, I love your videos. I have a request because it still causes me a lot of doubt, could you make a video about websocket?

I'm still confused.

So, when using services like this, I've secretly been using the repository pattern all along? 🤯

@theonlycaulfield

10 ай бұрын

No, this video perplexingly does not describe a repository pattern, as repositories are supposed to separate the db connection from the logic layer that is in the services/service layer. The author seems to be confused on this point when saying that he and others call the repository layer services. What he is doing is simply creating a service layer with the logic and db connection combined, which is what the repository pattern was created to prevent. The repo pattern is a common practice in enterprise software in the US, with both java spring and c# .net, where the intention is to isolate the db connection away from the service layer.

Hi Patric , Please clear the below issue I am facing. I am creating a GET request for search function. I am sending the whole model in GET. some of the properties in model is [required]. when I am sending the model the validation working. I don't want required validation for search operation. Is there any technique to remove the validation for GET Search method. Thanks.

This explanation is a bit not so correct. Services and Repository are two different patterns that perform different tasks. We use service to store the business logic such conditions and data manipulations.The repository pattern is used for data operations such as database CRUD operations

𝘱𝘳𝘰𝘮𝘰𝘴𝘮

Dude... im interested in an explanation of repository service, not DI. Stay on subject.