TIHIDI: Install and Configure Glass Mapper 4.x for Sitecore 8.x MVC Solution with Simple Injector 3.x

This blog post will go through how I setup Glass Mapper in a Visual Studio 2015 MVC solution for Sitecore 8.1. I have used other Sitecore ORM solutions but finally ended up liking Glass. Mike Edwards and Nathanael Mann were patient enough to teach me Glass in a short amount of time and the Glass training helped a lot as well.

Visit http://www.glass.lu/mapper/sc for more information on Glass Mapper for Sitecore.

TIHIDI: Stands for This Is How I Do It. I am going to write a series of blog posts going through how I do Sitecore related work. Hope it helps you!

As usual we will be using NuGet to get the current stable version of Glass, which at this moment is

Before we run the install package for Glass, make sure you have Sitecore.Kernel.dll, Sitecore.Mvc.dll and System.Web.Mvc.dll referenced in your project, which I do since I have been using the same solution for my blog posts.


Once Glass is installed, create two class library solutions, one called Mapping and one called Models.

I create hand coded (yes hand coded you lazy farts!) Models which are true .NET classes or interfaces. These will use .NET types along with Glass field types.

I do the mapping separately in the Mapping project. If the Model can auto map we can add it to the auto maps. If not, we create a specific mapping class for that Model to tackle the mapping.

Install Glass on these two projects as well.

In the SimpleInjector.cs class we will be registering all business logic functionality along with Glass mapping classes. Here is the sample code for SimpleInjector.cs:

Following this, lets get to the GlassMapperSCCustom.cs file in order to add our maps so that Glass can handle them. Here is the sample code for GlassMapperSCCustom.cs:

Once this is done we have to go and modify our App_Config > Include > SimpleInjector > SimpleInjector.config file to load the Initialize of the Simple Injector before Glass. Here is the updated config file:

Now lets add a simple TextBlock template in Sitecore for demo purposes, here is the sample template:


In the Models project add IGlassBase, here is the sample code for the interface:

Lets also add an interface to represent our template called ITextBlock. Here is the sample code for the interface:

Next we need a way to inform Glass as to how it needs to map these interfaces. We will begin my adding a GlassBaseMap class, here is the sample code:

For all simple mappings I dump them into a class called PureAutoMaps, so lets create a class and add that mapping. Here is the sample code:

There is no reason to inherit the IGlassBase except that it provides some additional attributes. You would need the Id attribute in order for you to make this editable in the Experience editor. Again this is just an example, we can highly simplify this as well.

Notice the way you are able to use ImportMap and pull in inherited classes/interfaces. Also notice how we used Automap and .Info in order to specify what Glass needs to do with the BaseTemplateIds. We will get into this in a lot more detail later.

Rebuild and deploy. Sites come up fine. Let check the ShowConfig.aspx.


If you have any questions or concerns, please get in touch with me. (@akshaysura13 on twitter or on Slack).


  • arpana kumari 8 months ago

    Hi Akshay,
    Can you please explain the pipeline (TIHIDI.SCExtensions.DI.Pipelines.InitializeSimpleInjectorControllerFactory) which is patched in “SimpleInjector.config” . I don’t see this pipeline explained in this blog .

  • akshaysuraadmin 8 months ago

    Thank you for reading my blog. The answer to that question is in another blog post here: http://www.akshaysura.com/2016/07/19/tihidi-install-and-configure-simple-injector-di-for-a-sitecore-8-x-solution/

  • Mark 5 months ago

    Hi Akshay,
    You say you dump all simple mappings in to a “PureAutoMaps” class but the definition of PureAutoMaps in your code block above is empty. What am I missing / misunderstanding here ?

  • akshaysuraadmin 5 months ago

    It is just used as a shell cs file. We are dumping multiple classes inside of that cs file.

Add your comment

Your email address will not be published.