MVC 3 introduced a new concept called a "Dependency Resolver", which greatly simplified the use of
dependency injection in your applications.
This made it easier to decouple application components,making them more configurable and easier to test.
Support was added for the following scenarios:
- Controllers (registering and injecting controller factories, injecting controllers)
- Views (registering and injecting view engines, injecting dependencies into view pages)
- Action filters (locating and injecting filters)
- Model binders (registering and injecting)
- Model validation providers (registering and injecting)
- Model metadata providers (registering and injecting)
- Value providers (registering and injecting)