Dependency Injection in .NET Core 3 (Second Edition) (Udemy.com)

Awesome. Thanks

Covering the dependency injection in .NET Core 3, which is very new, is really good. Interview questions will prepare every student for their next job interview too!

Into music in each time a new video begin is really annoying

I coded the provided hands-on project from beginning to end with .Net core 3 preview and Visual Studio 2019 preview. Everything works perfectly

tutor's speech not clear sometimes

Nice course about IOC and DI :) thanks

It was 2003 when the first time I heard about high cohesion and low coupling but to this day (15 years!) I really did not underestand how and when you use those concepts when coding!!

Thank you so much for putting this course together. It is very easy to follow, easy to underestand and super informative. You just proved that a course really does not need to include super advanced material to be good.

I'd like a little more hands on during the course. Seems pretty far into it before the first project.

Seriously thats what i was looking for, best of the best Sir, would you please create more c# courses. For everyone who strugle with DI, highly recommend buy this courses

The issue I had was that from the start I personally found the OO principles confusing. The examples of principles would have been far clearer against domain objects where the : Abstract Class / Concrete Class / Instance : hierarchy is clearer. Using non-domain classes to illustrate OO principles (when most of the classes are effectively singletons or static classes (i.e. just a collection of methods with no real state)) confused me.

Also the initial example of a web signup. It's good to have a real life example, but would be great if that example didn't 'encourage' terrible practice. There could be beginner programmers using this course and get the impression that emailing passwords and storing them in the DB is actually something that can be done.

Then onto the refactoring of the OO code into interfaces, concrete classes etc. I can't put my finger on it (due to the confusion between class and instance I mention before), but I suspect there is a little too much separation for the sake of separation in some cases. Sure you can take the implementation details out of the controller and leave it with just orchestration.. that bit I got.. but then when you also take the orchestration out of the controller then you just move both the orchestration and detail to another place without explaining what the advantage is. You seem to end up with exactly what you had before the refactoring, but just with one extra file to deal with .

Finally I think you go too far with the closed principle. You give the example of parameters changing on database select / insert statements and suggest pushing that down to a stored proc would solve that issue. However, unless you set up a fully dynamic system throughout your code (from user interface, to data classes to database) then changing the parameter list will always end up needing to change the Csharp code. So I don't really get the point. The other thing is that you seem to think that pushing logic to the database in the drive for OO purity is a good thing. To a point maybe, but all you end up doing is pushing code and all the issues with deployment, versioning, dependencies, logging etc into another area - the database - that has far less developed language, tooling and runtime capabilities than the one you are trying to push code away from.

The second part on the dotnet core dependency injection framework I am finding much better.

This course was excellent. Because it starts from a SOLID Principles, and Aref want to teach the people very deeply, and of course, I watched this kind, of course, other sites, but they weren't a big deal, but by this course, I learned more than dependency injection, and of course, I learned very profoundly. I suggest this course If you want to learn about dependency injection.

I've stopped watching the course because Mr Karimi's videos are too long which wouldn't be a problem if his narration and pronunciation wouldn't be so boring.

Nevertheless the knowledge he provides is helpful in understanding the courses core.