Area:
Replacing a component globally
Introduction
The following example shows how it is possible to replace a component for the entire system, and in this particular example how the built-in EPiServer CMS page tree can be replaced with a custom page list component. The registration required is done in an initialization module using the IOC container.
C#
// A simple component implementation represented with a dijit content pane on the client side
public class MyCustomPageList : ComponentBase
{
public MyCustomPageList() : base("dijit/layout/ContentPane")
{
// Add "Hello World!" as non-persisted content to the dijit content pane
this.Settings.Add(new Setting("content", "Hello World!", false));
}
}Then replace the page tree component using the IOC container by implementing the ConfigureContainer method of EPiServer.ServiceLocation.IConfigurableModule in an initialization module.
C#
public void ConfigureContainer(ServiceConfigurationContext context)
{
context.Container.Configure(container =>
{
container.For<IComponent>().Add<MyCustomPageList>()
.Named(new PageTreeComponent().DefinitionName);
});
}This will replace any creation of the PageTreeComponent with a new instance of the MyCustomPageList type that is created by the IOC container.
Do you find this information helpful? Please log in to provide feedback.
Last updated: Jul 09, 2014
