I had to support a legacy Web Forms application and while in the process of cleaning up several existing UserControls I had to explain to another developer exactly why using the ViewState to store custom properties wasn't worse than the current solution - which was, on every page
Unfortunately I've seen this issue in two different projects over the last few years. Sitecore uses a visitor identification sublayout to determine whether a site visitor is a bot or an actual human visitor. If you are a bot, your session times out much faster (1 minute, by
We have a non-Sitecore custom cache (which follows identical rules on both delivery servers and the authoring server) responsible for building up a hierarchy that is derived from a combination of Sitecore items and data in a custom database. The only trigger that can invalidate this cache is if the
After upgrading from Sitecore 7 to Sitecore 8 we started to notice that some of the dates shown across our site (in the format "22 Feb 2016") were showing a date one day earlier than expected. This date is pulled from a DateField on the item in Sitecore,
I had a few methods in a project that implemented some business logic that I wanted to be able to test from another project, but that weren't public. So how can I test them? Well... A testable method should be relatively self-contained. It should take a set of