22 Dec 2004
14 Mar 2011
Link to this post
Looking at the SF3 videos and Developer manual, it really does seem a lot easier.
Im not sure why everything seems to have got so complicated.
I don't think its a question of making things easy, I do like a challenge, but I have to balance cost and time of development. The project I want to use Sitefinity on needs around 10 custom modules I would think.
I just cant understand why for most cases you would even have to create a module as a complete new project. Surely it would of been easier to define the DAL in the SF back-end through a UI within SF.
Almost like creating a template, but you would create a custom "DATA" template, and then refer to it via the fluent api etc, I understand you can add custom fields but alas that is not always enough.
I admit I am not fully up-to speed on all that is SF, but the way I see it...
UI in back-end -> Define a Custom data template (Such As Products)
Define a UI template that allows you to use the Data Template for content creation (i guess it could be auto generated via the Custom Data Template)
Define a UI Display Template / lists whatever
and this generates either a custom ascx - ready to use in Visual Studio (Dreaming here perhaps) or something close to the above.
Ok im rambling on a bit now.. Just hope this gets sorted out. Telerik from my experience rarely if ever drop the ball, but I feel from my limited experience on this, that its not upto the usual Developer friendly standard I have come to expect from Telerik