Jul 05, 2014 02:11 PM|mystere|LINK
And here is the problem I see with the current design of asp.net vNext: it basically exposes its implementation details (which are fine if it wants to use them internally) and enforces them upon the "outside world", thereby shoehorning everyone into "its view
of the world".
I think you should re-evaluate the design. It doesn't do that at all.
What it does is bake DI into the framework, then it uses a conforming container interface that you can replace with any container you like. If you don't care and don't want to use DI, it uses a default internal container, and you never have to worry about
I really don't see how this does what you're suggesting.