Thank you very much for making this video. As stated, you're moving incredibly fast through this. This is my first time learning DI and I had to watch this 3 times to get the concept of what was done. It would probably help to slow down and explain why each step is taken and the negative impact of not doing so, or how it's removing dependencies. To me (and I have no clue about dependency injection) iit just looks like beautifying the code initially, I had to really repeat the video and test it to understand the concept - which I'm still kind of foggy. Not to nitpick, but I noticed you're moving so quickly there was syntax error in 8:29 and it still compiled? Furthermore, I don't think it's necessary in the end to tell me what I learned, this should be apparent, unless you're moving so quickly I had to be reminded that I missed something. Anyways, thank you for introducing Autofac and I look forward to more of your videos.
Thank you very much for this detailed feedback. This is the second video I did for my channel, and I learned a lot since I started in December 2018. One of my goals was to deliver as much value as possible without wasting time. As it turned out, I was moving too quickly for most people. I adapted in future videos, and I'm going to improve even further. I have a lot of respect for you that you went through the video multiple times instead of searching for another video. It shows how committed you are to learn this topic. The summary at the end does not take a long time, and I was always happy when the teacher at my university did it. I haven't received negative comments on this so far, but I'll consider leaving it out in the future. It depends on the topics of the video. About the syntax error, it seems to me like Visual Studio just took its time to update the error list. Usually, I do not take a look at the error list unless I tried to compile the code, and it did not succeed. Again, thank you very much for taking the time to provide this insightful feedback. I'll take everything into account for future videos.
very nice explanation , My understanding dependency injection is passing object param itself with autofac when we register class . in example userservice class we had constructor expect INotifcationService from object creation public UserService(INotifcationService notficationservice) { _notficationservice = notficationservice; } but we have not passed respective object. instead of that we register UserService , INotifcationService with DI var notificationService = container.Resolve(); var userService = container.Resolve(); so we calling directly an method userService.ChangeUserName(user1, "waran"); please correct me if am wrong Thanks
Thanks for this excellent video Claudio, I'm certainly a lot closer to understanding dependency injection having watched it! I'm not quite sure what's the point of adding the ProgramModule class at the end - what does this do? Also, for us beginners it might be useful to include another diagram at the end showing the relationship between the classes after refactoring.
Thanks, I appreciate your feedback, and I'm happy you learned a thing or two while watching the video. It was one of the first videos on my channel, and I'd include another diagram at the end if I would recreate it. The ProgramModule class allows you to group the registrations. You can use Autofac modules to organize registrations. I might create another more in-depth video about why that could be useful. But let's say you have a library. You can create a module class that contains all registrations, and then you could use that module class in the application.
Thank u for this great genial video, i got the point when u register the consoleNotification in the container because of its dependency from the user class but i see tht the userService has a dependency to user class so why the register inversly called instead of register the user class u re registering the userService class i didnt get it ? Could u please explaint ut for me
Great video, one of the most clear explanation. The resolve for the notification services it's not needed because at resolve the user service all of the inside dependencies that needed will be resolved, I'm right?
So you took something really simple and straight forward and made it more complex, adding more dependencies. Could've gotten the same result using the built-in IoC, with less code :-) Other than that, nice video.
I understand the criticism, and for this simple example, the built-in container would be enough. The video is targeted toward people who use Autofac at work (have no choice) and want to learn how it works. Still, I appreciate your comment; thanks for watching.
The built-in DI mechanism is great. In most projects, it's good enough. I might create a video about it. Autofac offers additional features that you might or might not treat as useful depending on your use case.
You didnt explain why you introduced the Autofac.Module at all. "We want to make use of Autofacs modularity feature".. OK, why? What is Autofac Modularity feature? When and why would I use it? How would I combine it with othe Modules?
Thanks for your feedback. Yes, I could have talked more about Autofac modules. I focused on how to get things done and didn't explain the Autofac modules a lot. To fill your gap and to provide you with as much detail as I can, I recommend reading the docs here: autofac.readthedocs.io/en/latest/configuration/modules.html
Good video! I am trying to learn Autofac from this video however run into the exception in Program class on line 15 saying Inotification service is not registered. What could be the problem?
Let me qualify that. Thanks for this video, and the one before it, both of which I've found really helpful. I'm grateful for your time and generosity in sharing what you know. I just wanted to offer some feedback on how this video was for me as a learner - I'm watching this because dependency injection in C# is new to me - I'm very much a student rather than a master. As a student, I'd love to have a little more time to take in the code that you've written in the different classes and interfaces - to see how they fit together. As a student, it's a challenge for me to stay with you at the speed that you are going - I would love the ease of a little more time and simplicity (perhaps in relating the implementation details back to a simple overview?).
Hey Rich. Thank you very much for your detailed feedback. In my first videos, I wanted to make sure that I am not telling boring stuff and taking too long to explain a concept. I learned from your feedback and a few other people that I need to slow down and that I can take a few more seconds to explain a topic without having a fear of annoying people. I'll consider that feedback in my future videos. I'm glad you enjoyed it, and you've learned something here. I hope to provide you with exciting videos in the future.
Useful video, but your claim in the summary that we've learned "How DI frameworks help your code" isn't actually true. You gave an example usage of a DI framework, but that's it. For the claim to be true, you'd have to first show what the equivalent code looked like *without* Autofac. And then show the difference with Autofac and explain why it's better with Autofac. Then your video would truly be fantastic.
Great question. The difference between dependency injection and service locator is the following: If you use a service locator it means that you have a hard dependency on the said locator. That means that almost every class of your system ends up with a dependency on that service locator. If you use the built-in dependency mechanism of the .NET applications, you don't have the same reference in every single class. You only reference the types/interfaces you need for your type. I hope this helps a little.
@@ClaudioBernasconi Yeah, thanks for the answer. I see, this way we only have locator\container dependency on the module that registers all the types within locator\container.
