Menu
I'm new to Ninject, and I was wondering if the scope of the kernel should be 1 per application. So should I treat the kernel as a singleton?
Thanks.
737
In Ninject the Kernel is the component that controls everything. We can directly bind the interfaces with implementations in the Kernel or we can pass them wrapped as modules. Whenever we need any implementation of the mapped interface we can get it right away from the Kernel.
Ninject modules are a good way to segregate our type bindings into distinct groups of bindings, which can be easily organized into separate files. Minimum requirement for a class to be accepted as a Ninject module is to implement the INinjectModule interface.
License. Ninject is intended to be used in both open-source and commercial environments.
InRequestScope method - it tells Ninject that one object of a particular type should be created for each individual request. InSingletonScope method - it tells Ninject that one object of a particular type should be created for all requests.
Yes, you should. More precisely - You should have one root container. It's OK to create context specific subcontainers.
101
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
