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 seven to nine in no time Target .NET framework As you can imagine a solution that has been around since Sitecore 7 has 'A LOT' of projects. My first plan was to visit each one and edit the target framework via the
Sitecore seven to nine in no time Indexes IndexField could not be found Back in Sitecore 7, this attribute was found in the Sitecore.ContentSearch assembly, as of Sitecore 8 it was moved to Sitecore.ContentSearch.Linq, it is used to
Sitecore seven to nine in no time Web Forms For Marketers Sitecore 9 is the beginning of the end for WFFM, thank God. Unfortunately, I am not out of the woods with my upgrade task as a new version was released. A new forms
Sitecore seven to nine in no time Sitecore Client Customisation WebEditCommand?! The WebEditCommand class once resided in the Sitecore.Client.dll, as of Sitecore 8.1 it has moved to Sitecore.ExperienceEditor.dll. Issues: The type or namespace name 'WebEditCommand' could not be
Sitecore seven to nine in no time ECM After working through upgrade issues related to ECM, the number of errors was overwhelming and intent of the customisations unclear, I concluded that pursuing a straight upgrade was not worth the effort involved.
Sitecore seven to nine in no time Analytics, move over DMS and xDB?! In Sitecore 7.5 xDB was introduced, this brought new ways of thinking about visitors to your website and tracking their journeys, but it was one big breaking change for solutions that had
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
Software Craftsmanship Plugins, why should I care? In my last post, Watch your Composition Root, while exploring how I keep my bootstrapping code nice and tidy, I point out that the approach workes very well when implementing the plugin pattern.
Sitecore Unit Tetsing and Sitecore I am a big advocate of TDD and would love to see interfaces on all of the Sitecore types. This is a big ask to put to the product team as they have
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
