C#, Software Craftsmanship, Sitecore, and Chips.
Start up bash in WSL2 issue the following: bash Install fish-shell sudo apt-add-repository ppa:fish-shell/release-3 sudo apt-get update sudo apt-get install fish Once finished exit and then issues below command: bash -c fish -cur_console:p Once its installed you can set up a fish profile in windows terminal
First thing we need to do is install the dashboard on your cluster: kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v1.10.1/src/deploy/recommended/kubernetes-dashboard.yaml The above is lifted form documentation that can be found here. Now the dashboard is installed we need to set
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
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 it very easy to lose control. So how can we mitigate this? Well, split up your registration