14 Dec 2010
30 Mar 2011
Link to this post
I am still evaluating Sitefinity, and of course I am comparing it to other content management systems. When it comes to defining custom content types, some content management systems allow you to create them completely through the UI (this is possible in Umbraco for instance).
The benefit of that is of course flexibility. But in my experience it also has downsides. For one, it means that these definitions are stored in the database, which is separate from code and thus harder to version. And creating custom content types through code has the benefit that you can write strongly typed templates (or widgets).
From what I know about Sitefinity, it makes more sense to code custom content types, because that way developers can use them through the API as well. I'm not sure about deployment though, it would seem that simply dropping an assembly would be enough to update existing custom content types, for example with new properties.