This post has been migrated from www.experimentsincode.com, we apologise if some of the images or content is missing
Back in 2013 I posted a survey about what Sitecore ORM developers were using and why, this led to the discussion that not all of them were strictly ORMS and the creation of a new term Object to CMS Mapper (OCM) (thanks to Robert Hermanussen and Mike Reynolds). I will use OCM through out the blog post to try and promote it's use. Before looking at the results of the survey I should point out that this survey is probably not completely balanced, I mainly promoted it via Twitter so those who responded are most likely people who follow me and who are therefore more likely to use the Glass.Mapper framework. The sample size is also rather small, I really appreciate that 46 people took the time to respond but one development team of 5 people all responding could easily swing the results. Having said that lets look at the results.
This question allowed respondents to choose more than one answer. The top three in order were:
The top three in order were:
Two thirds (28) of response were using Code Generation with their OCM, I am assuming that this was probably using either Team Development for Sitecore, Custom Item Generator or Classy SC.
It was encouraging to see that over 50% used their OCM to provide Page Editor support, this is one of Sitecore strongest features and if an OCM can't support this feature then the client isn't receiving the full feature set of Sitecore.
MVC and Webform usage are almost at the same level which I was surprised and encouraged to see. MVC relies on the developer being able to make models that can be