Continued Ninject support in ASP.NET MVC 6? -

i have been happily using ninject long time now, , it, faced difficult choice since release of asp.net 5 , mvc 6.

basically, out of gate, microsoft has revealed own dependency injection system; 1 knowledge has gotten lot of criticism. bigger problem lies how affects other libraries.

from another question asked , other resources online, seems ninject not work out of box mvc 6. though there "solution" given in form of verbose library microsoft.framework.dependencyinjection.ninject , ninject. trickier because library requires adding https://www.myget.org/f/aspnetmaster/ list of nuget feeds.

i have done digging , found library hosted; looks fine, seems work okay can tell, there few things trouble me.

• the library not appear headed ninject creators
• the library buried pretty deep in obscure repository
• the actual ninject resources online never mention it

so basically, concerned kind of band-aide, , support ninject (and other container libraries) dying out. there hidden information i'm not discovering?

• the library not appear headed ninject creators

that library, , seem these also, microsoft created samples of dependency injection providers removed in beta7. note link di in mvc 6 referenced original question says following;

these di container adaptors temporary , there reference; expect removed , replaced respective container owners.

as should be. microsoft should not responsible maintaining 3rd party providers.

• the library buried pretty deep in obscure repository

if not aware, asp.net 5 still in development. beta 7 available on nuget pre-release, there other sources including;

• https://github.com/aspnet/ (source code)
• https://www.myget.org/gallery/aspnetvnext (nuget dev branch builds of above)
• https://www.myget.org/gallery/aspnetmaster (nuget master branch builds of above [same question])

these sources maintained microsoft.

• the actual ninject resources online never mention it

as new development, 3rd party library providers must determine when (if @ all) provide implementations of products support new codebase. some, seen efficient wait until new framework officially released, api breaking changes still highly occur until point. whether support implemented @ of course providers resources, and/or in case of open source community.