Reputation: 2047
I downloaded the Ninject.Web.Mvc module and noticed that it did not contain the NinjectHttpApplication class which I discovered was in the Ninject.Web.Common and I have been using Ninject.Web.Common without the Ninject.Web.Mvc module and its been working well so far. So my question is.. do I need the Ninject.Web.Mvc library in order to use Ninject properly in an ASP.NET MVC 3 application? I wouldnt want to add an assembly/library that I would not use in my application
Upvotes: 0
Views: 134
Reputation: 9494
The Ninject.Web.Mvc
module gives you the ability to add dependency injection on your controllers. If you don't need to have dependencies on the controller contructors, you can get by without this library.
Read more here.
Upvotes: 2
Reputation: 93444
No, it's not required, but it does make your life easier. This library has the glue to hook up your MVC app, and how to take advantage of things filter injection.
It's not required you use it, but not using it means you have to write a lot of code yourself.
Upvotes: 1
Reputation: 3835
The short answer is no, you do not need it!
The not so short answer is still: No! But you'll need to make sure everything is handled correctly yourself, like wiring up the dependency resolver etc.
Upvotes: 1