ASP.NET Core MVC 2022 - 7. Dependency Injection + Repository Pattern

ASP.NET Core MVC 2022 .NET 6 - Dependency Injection + Repository Pattern

[kylecollie]

Nice analogy with the restaurant buzzer for async. Good job!

[theroostingroaster]

Man these tutorials are amazing, can't thank you enough Teddy.

[stanleyjekwu]

Thank you for what I'm learning from this series... I must complete this project. watching from Nigeria

[jftechdrones]

Thanks for the tutorials, have been very helpful so far! Died a little inside at 16:30 though lmao

[codegate]

I appreciated the refactoring lesson for DI/Repository pattern. Sometimes you skip over certain items without ever even briefly mentioning them such as why we use Scoped<>. Perhaps you'll go into it later, but I don't know that yet.

[liferunner_ua]

This simply should be liked for how you laugh on copy-paste programming temptation at 19:25

[JFresh]

Really enjoying this series. Can't wait for the next video! :)

[alzearafat]

Thank you so much, really helpful for beginners like me

[Eagler]

06:00 I prefer returning a tuple T<returnValuse, ErrorMessage), so in case of error, to know the message. Is there other approach?

[MyAutist]

Teddy, i my opinion, the MVC architecture reveals all the migty of interfaces. It often seems that there is no need in them untill you come acros this kind of projects... You define inteface, like You did here, then implement mock class for debug reson, then implement real data-oriented class and finaly, in one short string of code like "servies.AddTransient<Interface, Implementation>()", changing only one word (implementation) You change the whole behavior of your project! Isn't it amazin?! And thank You for yout series once more!

[bjornhellgate]

This has been a really good tutorial so far, but why does some of the Club description say "This is the description of the first cinema" instead of club? are we secretly making a cinema page?

[xavrock]

Hi. In 10:13 Why didn't you use SaveChanges ?

[hachiq]

Thanks for that)
I wanna ask what is the point to make actions Task<IActionResult>?
Why don't just leave them IActionResult

[Eagler]

Why having one file per interface?
I prefer having them in one file so a) I have one file open and b) I can find easily with the dropdown.
Same with classes.

[codegate]

Why did we make the Get code in the Interfaces Task<>?

[huynguyenluonggia]

hello everyone, for this project, I want to add a folder named Service can I add services that I use?

[siemkagospodarzu]

Can you explain why the hell are you creating interfaces instead of just putting these methods to these repository classes? Interface is useful when you use it in multiple classes.

[kishorl]

Can you tell me why we need this pattern, it's so confusing

[tlhsieh]

Good video. Could I know the difference between "_context.Add(club);" and "_context.Club.Add(club);" ?

[TheAndyCooperz]

What's your opinion on separating your project into multiple solutions e.g. Hosting, Core and Persistence?

Also, you copied all the code from one interface to another, what is your opinion on having a base interface with definitions that are shared amongst many repositories then in your repository interfaces having definitions that are specific to each repository?

Great videos by the way :)