This topic describes how to create an initialization module to work with the initialization system in the Optimizely platform.
How it works
When you create your own initialization module, add a reference to EPiServer.Framework.dll. The following Initialization code example shows how a property is set up with a default implementation in Initialize and then the process is undone in Uninitialize:
public class SampleInitialization : IInitializableModule
public void Initialize(InitializationEngine context)
public void Uninitialize(InitializationEngine context)
- The initialization engine makes sure that your code executes in a single-threaded manner.
You do not need to lock regions when you deal with shared state. This guarantee is only made for Initialize and Unintialize when you execute through the initialization system. If you have custom code that makes calls directly into your initialization module, then you may need to deal with multi-threading issues.
- Remember that the initialization system tracks the initialization state of your module.
- Do an implementation of Uninitialize.
Anything you do with Initialize you should undo with Uninitializein the reverse order of Initialize. This is especially important if you write integration tests that reset application between test runs.
- If you are using the CMS API make sure you are adding a module dependency to CMS using [ModuleDependency(typeof(EPiServer.Web.InitializationModule))].
Last updated: Jul 02, 2021