Notes

[28-Dec-2017]

Inside ASP.NET MVC: IDependencyResolver - Service locator in MVC All types inside ASP.NET MVC3 framework are being resolved by IDependencyResolver. The design goal of this interface is to provide flexibility and decrease coupling between components. In fact, IDependencyResolver is pure service locator. This interface should be used by IoC containers, not by 727D individual developers.
-Create instance of a class with dependencies using Autofac Some very basic dependency injection discussions
--Composition Root discusses what is composition root. By Mark Seeman himself.
---Compose object graphs with confidence talks about "Register Resolve Release" pattern and the idea there should only be a single composition root. It has really great comments at the end.
---Reused Abstractions Principle - speculative generality is considered a code smell. OO Design to counter the trend for speculative abstractions. Most particularly, the trend for putting interface everywhere, regardless of whether that interface represented some commonality between two or more types of object. There are many overly simplistic formulas that mask more fundamental and nuanced principles. Code clutter.
---Role Interfaces - distinction between role interfaces and header interfaces.
---Decoraptor TBD

Provide feedback