Is Umbraco's ContentService poorly designed and inherently broken?
Been looking at IContent and IPublishing types and fear the Umbraco has some flaws that will get in the way of building large scale applications with domain driven design.
IContent is for direct to database CRUD operations and ContentService use IContent types.
IPublishedContent gets content from the cache and is therefore faster and preferred on the front end.
All good until you create your own Strongly Typed POCO's. If you inherit from IPublishedContent for easy of use in your views and document types, you start to hit problems when you want to create new content with those types. ContentService.SaveAndPublish wont take a IPublishedContent type.
Is there another way to deal with your own Strongly Typed entities or, as I fear, has Umbraco grown into a framework with a split personality that doesn't accommodate simple domain models!?
Is Umbraco's ContentService poorly designed and inherently broken?
Been looking at IContent and IPublishing types and fear the Umbraco has some flaws that will get in the way of building large scale applications with domain driven design.
As discussed in this post http://our.umbraco.org/forum/developers/api-questions/46631-Getting-Umbraco-Content-IPublishedContent-vs-IContent-vs-Node-vs-Document
IContent is for direct to database CRUD operations and ContentService use IContent types.
IPublishedContent gets content from the cache and is therefore faster and preferred on the front end.
All good until you create your own Strongly Typed POCO's. If you inherit from IPublishedContent for easy of use in your views and document types, you start to hit problems when you want to create new content with those types. ContentService.SaveAndPublish wont take a IPublishedContent type.
Is there another way to deal with your own Strongly Typed entities or, as I fear, has Umbraco grown into a framework with a split personality that doesn't accommodate simple domain models!?
is working on a reply...