Something I had a look at quite a while back was the fluent configuration api in Glass. Unlike many developers, I am absolutely 100% fine with adding spaces to field names and don’t like using attribute based configuration in Glass. I talked about this in some detail a while ago in Introducing Glass Maps. I have since been through several iterations and finally settled on one that I like and therefore contributed to Glass itself. In essence, it is simply a neat way of bundling your fluent mapping into discrete units, which allows you to keep the mapping isolated from your POCO’s.
I understand this is not to every developers taste, but if you like to see clean .net objects, this my be the mapping configuration type for you.
Glass V4 is nearly upon us, and I am pretty damn excited! This series is looking at the latest features and improvements they have to offer.
In this blog post I am going to look at the changes to the registration API, particularly the removal of the dependency on Castle Windsor and how they have changed the face of Glass Mapper on the Sitecore platform.
Following on in my series looking at the new features in Glass Mapper v4.
One of my favourite features of Glass V4 is the new Caching feature. This at at in its simplest form allows you to cache the object that Glass produces, much like we do in regular .net development for slower running processes. In this post I will describe some more about caching, how to set it up and what it does.