So far we know that what are the things we should not do in MVC dependency injection. Now it's the time to understand how exactly we should do dependency injection in MVC applications, especially with this kind of scenarios of home controllers and all. So let's see that, I'm going to right click on my component folder, and inside this we are going to add a new class. And I'm giving the name of this class custom controller factory.cs. Now, this is something which is my own class custom controller factory, but I've given the name like this because to do dependency injection in MVC, I'm going to use one of the predefined facility of MVC, which is coming from an interface with the name II controller factory. Now if you remember in the previous videos, I have discussed with you that There are 13 containers of IOC which we can use and those predefined containers of IOC s are going to help us to do inversion of control and dependency injection in some of the applications.

Now, in this case, we are going to use one of the predefined thing which is known as I can do a factory interface which helps me to create my kind of instantiation with the dependency injection of any custom controller. So, let's add a namespace using system dot web dot MVC, which is a main namespace of MVC we already discussed this thing and now using this I can add one interface. So, that is I controller factory you can see is there which is pretty fine. Now like all the interfaces when we have interface we are going to implement this interface. And if I implement this interface, you can see I have three predefined methods which are coming into this. So the there is a method with the name create controller, which actually helps me to create an issue instantiation of my controller with my kind of parameters and customization, there is a method in the bottom, which is release controller, which is technically going to dispose that particular controller instance from the memory as and when we need that thing.

And there is a method in between which is get controller session behavior, which just helped me to maintain the behavior of that particular controller in a particular session. So, this is something which I'm going to utilize now. So I'm going to add a code inside this and I want that this custom controller factory class can help me to create my kind of instantiation of a logo. And that's why our core goal goal like this equals to new and then we can instantiate with any of the concrete implementations, we have only one right now, which is default logo, so I'm instantiating with this. Now this logo is the instance of Before logging, and then based on this, we need to associate with a home controller. Sampling a variable controller equals to new.

And then I'm going to create an instance of a home controller. The moment I do this thing, this is not taking home control right now because I do not have a nice face of controllers. So I'm detecting that now. And inside this, I'm going to pass my logo so that this one is going to associate with my parameterised constructor. So I hope you agree with me this is an instance of home controller and the moment I pass a parameter, this will go to Home controller and this will call my parameter constructor, which is associated with the logo. Now exactly after this we are going to just type one line and that is we are going to return controller.

So this create controller is He's not actually creating a new controller is creating my own controller with my kind of parameter. And that customized controller we are going to return from this particular method. Now once we are done with this inside the second method, which is giving me the session behavior, we are just going to return whatever session behavior we have dot default so we don't do any fancy thing inside that. And in fact the release controller we have to dispose the controller when we need so I am just calling it disposable. I'm giving a name of that. disposable equals to controller as disposable and we'll make sure this is going to be a small see Santa Claus controller.

It's just my kind of variable and now once we have this disposable I'm just going to check if this disposable is not equals to No. If we have something in that then we are just going to call disposable dot dispose this this course is a predefined method which will dispose that thing. This core is super simple, I hope you're able to understand this thing if you have ever disposing the object using a disposable. So, we have a simple controller factory interface which is implemented inside the class and we have three methods create controller, get controller session behavior and release controller and we have associated this with our home controller and we can dispose that as and then we need that thing. Now once we are done with this Now the next step is task is how we can associate this custom controller factory with our home controller always.

To do this thing we have to take the help of our global dot ASX. So we know that in MVC application you already Have lobola ASX so I'm going inside this global dot ASX and I'm going to add some lines of code inside this. So we have application start, which is the starting point of application execution exactly outside this application start, I want to create my own method. So I'm creating a method, private word, and I'm giving a name of this method that register my factory. So, this is going to be registering my factory which we have created and inside this method, we are going to write some logic. So I am using my interface I controller factory and giving a name of this like factory equals to new and then we are just going to call our custom controller factory into this.

So we should have the class which is custom controller factory and specifying it here. I'm going to pass on this because it's not detecting we just need to add a reference of this. So, we are just adding these components inside this and now this factory is the instance of custom controller factory same way inside the register my factory I can create one more controller factory kind of variable which can associate with nearly another kind of custom controller factory The only one so we are just utilizing this one inside this and now I'm calling controller builder, which is another predefined class helping me to deal with this my custom controller factory. So controller builder dot current dot status, the method set controller factory in which we are specifying that we are going to set this factory as a current factory. The moment we are done with this, you can see that this method is just helping me to create my own factory and registering my factory into that.

Now all I need to do is I need to call this method on the top of all of this So it's something like this when the application has to start first is going to register my own factory with my kind of things and with that is going to associate my controller factory instance. Once that is done, then all the predefined things will happen and in this, your predefined home controller or the other controllers are going to work. In short, without touching the high level modules, we have just created our own low level modules, which are based on this abstraction. If Microsoft did not provide this kind of icon to the factory, that's also possible that we can create our own containers and we can create this thing manually. But because Microsoft has provided this thing specially for MVC, they're using this controller factory and using this we are just configuring this thing in such a way that my home controller is now connected with my ilogger without disturbing the predefined things without disturbing the high level modules.

Our high level module and low level module both are connected with abstraction. So by following dependence envision principle with inversion of control with dependency injection in MVC. This is what we have done inside this. Let me click on Save all. And. And if you want to check this thing, just, you have to do one thing.

I'm going to put a breakpoint one in my default constructor, and another one in my parameter constructor. And I want to see that actually, this is hitting directly to my parameter constructor or not. Because if everything is correct, this will not go to my default constructor at all. This will always go to my parameter constructor when I run this application. So let me change my browser to maybe web browser, which is Microsoft H. And inside that, we can choose the browser. So I'm just going to select maybe H or chrome or whatever is there.

And then I'm going to click on Save All I'm going to run this. The moment we run this thing is going to start debugging because I'm running with debugging. And if it is setting a breakpoint, I want to see which one breakpoint This is hitting. And you can see that when I'm running this thing is now hitting my breakpoint. And this is directly hitting my parameter constructor. It's not at all going to my default constructor.

And that's what we have achieved with the help of this dependency injection inside MVC application. I hope you're getting this application code. And same way if you want to create multiple custom controller factories, or you want to create some more concrete implementations of ilogger you can use the same way into your multiple controllers. I hope you understood this video. Thank you