This may be stupid question, but I am looking at Ninject sources and don't see NInject registering its own controller factory. I also don't see any IControllerFactory
class in Ninject.Web.Mvc
assembly. Am I missing something? How does Ninject create controller and inject parameters into constructor?
- Lets say we are looking for "/Task/Index".
- Ninject MVC applications use now
DefaultControllerFactory
, the same as non-Ninject applications. DefaultControllerFactory
finds type for controller (TaskController
).DefaultControllerFactory
has internal class calledDefaultControllerActivator
.DefaultControllerActivator
has method calledCreate
, which returns controller instance.DefaultControllerFactory
asksDefaultControllerActivator
forTaskController
type instance.DefaultControllerActivator.Create
usesIDependencyResolver
. This is whereNinject
comes in. SinceNinject
implements its own resolver and sets it at the start of application, he gets request forTaskController
instance.- The rest is easy.
Ninject
finds constructor for this type, injects parameters, returns controller instance.
MVC3 now recommends the usage of the IDependencyResolver
interface instead of the good old IControllerFactory
when dealing with DI. You can look at more details of this interface here.
This is the new Ninject class responsible for injecting the dependencies.
Since controllers are concrete types, Ninject will do self bind. Below is a snippet from ninject.complex.com
Bear in mind that only concrete types can be self-bound; abstract types and interfaces won't work. Also, if you request an instance of a type that can be self-bound, and there are no bindings defined for the type, Ninject will automatically create an implicit self-binding. It's up to you whether you want to define your bindings explicitly, or let Ninject figure it out.
If you do need to inject parameters into the constructor. You can create a class inherits from INinjectModule
and do the binding there.
© 2022 - 2024 — McMap. All rights reserved.