Sitecore DI container references vs system boundaries. In my post, Watch your Composition Root, I explore how to empower plugins to be apart of the application bootstrap process. After sharing this two friends of mine, Rob Earlam and Sean Holmesby
Sitecore Service Locator Pattern or Anti-Pattern? For a long time now I have considered the Service Locator an Anti-Pattern, but recently I have come to question this resolve, is it black and white? Maybe not. Mark Seemann first introduced
Sitecore Two containers are better than one. Sitecore is a fantastic CMS that does many things right, and from version 8.2 the list also included Dependency Injection. It's great to see the product embrace IoC, the framework's code is
Dependency Injection Watch your Composition Root IoC is a great pattern that can help make business logic easier to maintain and independently test, all while decreasing complexity. However, in large applications object dependency graphs can become quite complicated making
Unit Testing Test First Drop Bear I love TDD, but there could be a Drop Bare[1] waiting for you. The whole Red Green Refactor cycle is great but, can it be taken too far? When I started coding
Dependency Injection Gravyframe For the last few months I have been working on a boilerplate and example of how I think a website should be built on top of a .NET CMS. The basic idea is
Dependency Injection Dependency Injection an attempt to explain I was explaining to a friend the other day what dependency injection was, and even though I use this in almost every class I create I could not come up with a simple
