This post was inspired by a famous subreddit called “explain like i’am five” where people asks tough questions to be explained in a simple way, like how do we do for a five years old child. There, you can find interesting questions like: this and this. Beware! you can get addicted to ELI5. The foundation…
Before, read my other post explaining why this subject is so important. The idea around the Composition Root pattern is to create an assembly exclusively to register all the dependencies, the architecture will look like this: The CompositionRoot.dll references all the other projects, except the View (see the red arrow). Note that the View.dll (which…
Before, read my other post explaining why this is so important. This architecture is about to make make each assembly register their own dependencies. The idea is to develop a class that receives the DI Container by parameter and register the dependencies in that container. This class is called by reflection from somewhere next to…
The Scenario: You are developing a system, applying the S.O.L.I.D concepts and de inversion of control principle, you decide to use dependency injection and some DI Container. The literature and the patterns tell us that the dependencies should be registered as close as possible to the entry point of an application, that is, usually the…
The Scenario Both Visual Studio Team Services (VSTS) and Github are incredible services, both have strenghts and weakness, to choose between each one is a thought task. VSTS is full featured, the features present in it is suitable for big enterprises. Private repositories is the default and in the free plan i can share my…