Jul 08, 2014 01:17 AM|mystere|LINK
I know and understand that it is easy to BYOC and I can't see any situation where, if I wanted a container, I wouldn't bring my own. As soon as my app is large, I will want to do things like scan an assembly and auto register services based on conventions which
the baked in implementation doesn't provide. Which I guess is the essence of my point, if you want a container, it's going to be one with advanced features. I'm happy for the framework to use a conforming container as long as I don't need to know about it.
You seem to keep missing the point that MVC's default container is just that, a default.. You can replace it with any container you want, with all the full functionality of that container. Why do you keep arguing that you can't do this? The conforming
container is an *interface*, which supplies the basic functionality that MVC needs, not what your app needs. If your app needs more functionality, then you simply use your containers native configuration. What's so hard to understand about that?