Episerver resources for new developers

Episerver is a comprehensive CMS system based on C# which is trusted by the world’s leading brands. It also ranks very high in the Gartner Magic Quadrant for Web Content Management report each year.

At Valtech Episerver is implemented for the largest platforms like Action.com, BeterBed.nl and Aegon. The main competitor for Episerver is Sitecore which we also implement regularly at Valtech. In my own experience Episerver is more accessible and more easier to learn than Sitecore. But, when being confronted with a new CMS system there’s a lot to learn!

With this blog post I would like to share some very valuable resources which can come in handy when developing for Episerver.


If you need support from Episerver in any way don’t hesitate to contact them.


Episerver has a big community with enthusiastic developers. Feel free to post your questions on the Episerver forum.


The brightest minds share their experiences with Episerver on their blogs. Check them all out here.

Colleague & Episerver MVP Jeroen Stemerdink is also blogging about his Episerver adventures: https://jstemerdink.wordpress.com/


The Episerver documentation is really good and not to be missed. Essential reading when setting up and developing for a new Episerver platform.

The user guide is available online and as a PDF copy.


Episerver has fully embraced the NuGet system for the delivery of all their packages. The complete CMS and Commerce system can be installed by only using NuGet packages further improving the overall development experience.

NuGet package list: https://nuget.episerver.com/
NuGet feed Url: http://nuget.episerver.com/feed/packages.svc/


Episervers offers various courses to get you up to speed with Episerver. Check them all out here: http://www.episerver.com/services/education/overview/


Episerver does not function without a proper license in place. You either create a license for development purposes or you create a commercial license for your test, acceptance and production environments.

Read all about it: https://license.episerver.com


Another great way to learn more about Episerver and to meet the community which supports it is to visit the various Episerver events and meetups.

Demo kits

Episerver has developed various demo kits, also called reference architectures, which showcase all the latest features and which run of the latest version of Episerver. It’s a great way to learn how you can use and implement the Episerver products and their API’s to your advantage.

Quicksilver: https://github.com/episerver/Quicksilver
Alloy: https://github.com/episerver/AlloyDemoKit


Modules allow you to extend the out of the box Episerver functionality. A lot of modules are available for free. The modules are also called add-ons.

We especially like:
Database Localization Provider: https://github.com/valdisiljuconoks/LocalizationProvider
404 handler: https://github.com/BVNetwork/404handler

Happy coding!


Sitecore performance analysis with New Relic

logo_NR-twFor several years already an application performance monitoring tool called New Relic is the default instrument to get detailed performance metrics from many of our web platforms we develop at Valtech.

We use it to gather detailed insights in the inner workings of many of our applications, even in real-time when they run in a production environment. It allows us to find and troubleshoot performance related issues fast. Not only in the .NET backend logic with the APM product but also in the logic happening on the frontend with the Browser product.

A small bump in the road

One of the technologies we implement at Valtech is the Sitecore Experience Platform. Wouldn’t it be great if you could get detailed performance metrics from your running Sitecore instances on production? I took on the task to find a suitable tool to make this a reality. After evaluating AppDynamics and LeanSentry I found the most suitable tool in New Relic. Although New Relic had great features and a very easy to use web dashboard it didn’t have support for Sitecore out of the box. As you can read on the compatibility page New Relic only supports Umbraco and Episerver CMS technologies but not Sitecore. The main issue is that all transaction (web requests) are reported in New Relic with their physical layout file, layout.aspx for example, and not with the requested URL. Which in turn makes the transaction and web request overview pretty useless.

Challenge accepted

I like a good challenge so this challenge was accepted! The nice thing of New Relic is that it also provides a SDK which you can implement in your web app. As it turned out, this SDK can be used to change the behavior of New Relic at run-time. One method grabbed my interest, the SetTransactionName method. This method can be used to set any transaction name for the current request. Exactly what we need but when to set it? After lots of trial and error I discovered that the only reliable point in time was during application initialization and to be precise, during the ASP.NET OnAuthenticateRequest life cycle event. To learn more about all the life cycle events see: https://msdn.microsoft.com/en-us/library/bb470252.aspx

At this point in time we also have a Sitecore context to play with. The Sitecore context is essential to grab the current site and current item being requested. In this particular case the New Relic implementation had to support a platform hosting +20 different websites. So, during the OnAuthenticateRequest we grab the current site and item and use this to construct a correct and friendly transaction name.

You are also able to ignore particular requests passing to New Relic. For example requests to static resources or images from the Sitecore media library. The IgnoreTransaction method can be used to achieve this.

A module was born

The final solution was the implementation of a custom NewRelicHttpModule which you can download from the Sitecore Marketplace.

Custom Sitecore tasks

Although New Relic is great for profiling the .NET framework and your own custom code it will need a hand if you are doing fancy stuff like starting new threads during run-time. If you create custom Sitecore tasks which run in the background then the Sitecore task runner system will create a new thread to run your task in. In this case your background task will not be picked up automatically by New Relic. The solution is to tell New Relic about your task by specifying your classes and methods in a custom New Relic instrumentation file. The extensive New Relic documentation will tell you in great detail how you can accomplish this.

A Sitecore task can be seen as a non-web transaction. By implementing custom instrumentation all your Sitecore tasks can also be made visible in the New Relic dashboards.

A broken Sitecore Rich Text Editor

When you also use New Relic to measure the frontend performance with the Browser product and when you also have this running on your Sitecore CMS instance then you might run into issues with the Sitecore Rich Text Editor, it will break. The reason is because New Relic by default automatically injects a piece of Javascript in any page to be able to measure all operations in the browser, which conflicts with Sitecore.

The solution is simple, you can disable the frontend performance monitoring per application and thus for the CMS instance. See the documentation on how to disable the browser monitoring feature.






Sitecore 8, AutoFac & WebForms

At Valtech we recently upgraded a dated Sitecore 6.6 platform to Sitecore 8.2 initial release. The platform contained multiple websites developed with Microsoft WebForms technology and used Autofac as the Inversion of Control container.

Integrating the Autofac modules

The comprehensive Autofac documentation contains a topic on how to integrate the latest Autofac in a WebForms application. Adding the modules to the web.config was easy, it’s our best practice to use config transformations per environment for any necessary changes to the default Sitecore files which include the Web.config file.

An example of the XDT transformation used to include Autofac in the Web.config file:

 <modules runAllManagedModulesForAllRequests="true" xdt:Transform="SetAttributes">
[@name='SitecoreHttpModule'])" />
 <add name="ContainerDisposal" type="Autofac.Integration.Web.ContainerDisposalModule, Autofac.Integration.Web" preCondition="managedHandler" xdt:Transform="InsertBefore(/configuration/system.webServer/modules/add[@name='SitecoreHttpModule'])" />
 <add name="PropertyInjection" type="Autofac.Integration.Web.Forms.PropertyInjectionModule, Autofac.Integration.Web" preCondition="managedHandler" xdt:Transform="InsertBefore(/configuration/system.webServer/modules/add[@name='SitecoreHttpModule'])" />
 <add name="AttributedInjection" type="Autofac.Integration.Web.Forms.AttributedInjectionModule, Autofac.Integration.Web" preCondition="managedHandler" xdt:Transform="InsertBefore(/configuration/system.webServer/modules/add[@name='SitecoreHttpModule'])" />

Implementing Autofac container initialization at startup

The next step involves implementing the IContainerProviderAccessor interface in Global.asax. The Autofac dependency injection modules expects that the HttpApplication instance supports the IContainerProviderAccessor interface. And this is a bit tricky to implement in a Sitecore 8 solution.

Normally you would create a custom HttpApplication sub class, include the Autofac magic in this class and point your Global.asax file to this class like this:

<%@Application Language="C#" Inherits="My.Custom.HttpApplication.SubClass" >

When using Sitecore 8.2 initial release we noticed that the Autofac container was not being properly initialized at startup and therefor dependencies could not be resolved at run-time.

After some research we noticed that the Application_Start event handling method did not fire at all in our custom HttpApplication class and which is responsible for setting up the Autofac container when using WebForms technology. According to Sitecore support the reason is that if we have several Application_Start methods (like in this case), only one will be called. It’s Sitecore.Web.Application.Application_Start method, since it’s declared first in the chain of derived types. Ideal solution would be to override that method, unfortunately we can’t do that since it’s marked as internal in the base class. This Sitecore behavior has been registered as a bug with the reference #126372.

We didn’t want this bug to be a showstopper and we discovered a simple workaround. The workaround consists of simply copying the whole Sitecore.Web.Application class to our custom class. And suddenly the event methods do get picked up at start up. Tooling like dotPeek can be used to decompile the Sitecore assemblies.

Getting Autofac 4.x to work with Sitecore 8.2 & Solr

If you are using Solr for your scalable Sitecore 8 platform then your are most probably aware of the official Sitecore documentation on how to setup Solr. The documentation also describes how to configure an IOC container like Autofac.

Unfortunately, the documentation and the supplied Sitecore support DLLs are verified to work with AutoFac v2.5.2. But as you can imagine Autofac v4.x contains breaking changes compared to Autofac v2.x.

If you want to use the latest AutoFac then you will need to include the sources of the by Sitecore supplied AutofacContrib project in your own project. The classes include AutoFacInitializeSolrProvider, AutoFacSolrStartUp & AutofacServiceLocator.

Also change the type in Sitecore.ContentSearch.Solr.DefaultIndexConfiguration.IOC.Autofac.config to your own AutoFacInitializeSolrProvider class, for example: My.Namespace.AutoFacInitializeSolrProvider, My.Namespace

A small refactoring in the AutoFacSolrStartup class was also needed.


ServiceLocator.SetLocatorProvider((ServiceLocatorProvider)(() => (IServiceLocator)new AutofacServiceLocator((IComponentContext)this.container)));


var csl = new AutofacServiceLocator(container);
ServiceLocator.SetLocatorProvider(() => csl);

Soon we will start the upgrade to Sitecore 8.2 update-2 and then we will know for sure if the Global.asax startup bug has been resolved.