Code Generation

In my previous post, I’ve described the benefits of composition pattern over inheritance in code generation and mentioned that it simplifies restoration of models from reflection. From my point, this is a huge plus as it enables the creation of developer-friendly modular architecture in Sitecore. I do not think that someone still has problems with a creation of an update package with Sitecore config transforms, but it is not possible to install an update package in your Visual Studio solution....

If you do Sitecore projects and have never tried to create strongly typed models, then most likely you are doing something wrong. :) Why? As soon as your project grows a bit, the logic becomes more complex or you decide to refactor a few components, you will suffer from all magic things - strings, numbers, GUIDs. Of cause, there are a few things that you can do about that. Available Options You could create a file with constants for templates and field IDs, which would help you keeping references in one place and make them more manageable....