Join GitHub today
What are your plans in creating and maintaining a Ninject adapter for the ASP.NET vNext DI system? #177
I'm interested to know whether or not the Ninject team has decided to take over the maintenance of the ASP.NET DI adapter for Ninject that the ASP.NET team built.
As discussed by Mark Seemann here and on the Simple Injector forum (in discussion with David Fowler) here, implementing such adapter has some serious downsides; even for Ninject. The discussion on the Simple Injector forum also shows a very compelling alternative that is applicable for any possible DI container (and applicable when practicing Pure DI).
So I'm very interested to hear whether your team is planning to support such adapter, or whether you favor a guidance similar to given on the Simple Injector forum. I really like to hear your opinions and motivations behind this.
referenced this issue
Mar 14, 2016
I think an "official" response from the ninject core team would be very useful. It feels like autofac have made a statement with their choice of support. But I'm unsure if ninject's opinion, whether there currently isn't an adapter because it's the wrong thing to do (as SimpleInjector suggests) or whether it's something that's coming in the future.
As people begin to migrate their code to MVC 6 this question will come up a lot and it's an unknown at the moment probably making people consider autofac (rightly or wrongly) as there is an official response.
Since you are using the Missing-Core-DI-Extensions, please consider sharing your experience with them on this thread. It's important for Microsoft to understand that the omission of these extensions is a problem for Ninject users as well and to know how well these integration points work.