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 properties window, but after the first three projects of about 70, I thought to myself "This

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 map an index field to a POCO property where the names are different, and the default provider

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 solution called Sitecore Forms looks very promising, and my money is on WFFM moving into maintenance sooner

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 found (are you missing a using directive or an assembly reference?) 'xxx.Execute(CommandContext)': no suitable

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. If you have many customisations to ECM as this solution did, it might be worth your time

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 bespoke analytics code. The unfortunate thing here is more often than not this shift in thinking about