Jul 02, 2014 05:31 AM|adrianhara|LINK
I would be very curious to hear more from the asp.net team on why we can't simply go the abstract factory route and we're leaning towards the service locator / conforming container again? I can partially see the appeal of making stuff look easy
for the users (i.e. they don't have to implement 5 interfaces, just one), but I sincerely believe that a few bits of written guidance would take care of this, with the added benefit of teaching people good design (ploeh's blog posts are a great example of
how such docs might look like). And in the end, if we really really want to have one interface, why not simply leave other extensibility points in place, for the cases when they'd really be needed?