We had a nasty little bug in one of our development stage Episerver projects. Everything ran and worked smoothly, but one day Episerver’s error logs started to report an exception regarding the Episerver.Find.Commerce module. However, the site seemed to work properly so the bug hunt could be scheduled to another day.
Things escalated when Episerver made some error handling changes in the Episerver.Find.Commerce version 10.1.1.
Interfaces are more or less basic stuff in programming and in Episerver development. You probably have seen these guys (IThisAndThat, IEtc..) all over the reference solutions (AlloyDemoKit, Quicksilver, …). In this blogpost, I’ll be taking a concrete approach how to make one of the AlloyDemoKit’s content blocks more compatible with other content elements using an Interface.
Continue reading Using Interfaces to get more compatible content elements in Episerver
In the previous post, I wrote about profiling your Episerver site and how important it is to spot bugs and performance issues early on. Now it’s time to create some traffic in your development environment and analyse how well your site performs under load.
Continue reading Testing your Episerver site performance with Netling
We all know that bug happens. They are inevitable during development, and basically in every step-in software lifecycle. The thing that makes a difference, is to catch them as early as you can. You do not want to be in a situation where production site is suffering huge performance issues with only handful of requests.
Continue reading Smashing bugs from your Episerver site with Stackify Prefix profiler
Ever had a problem where you would like to open or get the full public address of a page from the editor view in Episerver? Or is it a problem at all?
Continue reading Adding a “View on Website” -button to context menu in navigation tree
