Is the formal structure of the application too large?
Our store designs and builds custom software applications for varying vertical industries. We are currently using a modified version of Csla for most of our development.
It is a great framework , it supports the size of the way to communicate with the database, directly, delete, WCF, etc. It offers a ton of features, many of which we don't use. The benefits of a career are numerous, the big one being Rockford Lhotka is a step forward when it comes to technology new , which means we don't have to do research. The downsides to structure are the fact that you are at the mercy of how the creator implements the changes and technologies and all the many features you don't use.
With the advent of Linq-to-Sql, we are seriously looking at switching, providing a lot of everything that is generated is purely data access, but by creating partial classes, we could extend data access and provide business logic. We could also create some formal interfaces for working with business logic. Could use / create our rules manager etc. In a nutshell, we will be developing our own application infrastructure.
I noticed while Jeff Atwood was discussing the ASP.NET MVC framework at PDC 2008 , he was mostly working with one project and he also looked like he was extending Linq-to-Sql with partial classes. This architecture seems to demonstrate the fact that the code is easy to maintain, new features are quickly added, and bugs are quickly fixed, and that it works well ... most of the time.
I'm just curious to know what are the other thoughts of users? Am I crazy to give up our structure so that something I perceive is easier to use and more maintainable ?
source to share
The disadvantages of the framework are the fact that you are at the mercy of how the Creator implements changes and technologies and all the many functions that you do not use.
You would seem to run into these same cons with LINQ, so keep that in mind when making changes. In any case, you should do a full analysis before making such a leap, perhaps placing one of the smaller existing applications or a subset of one of the applications as an example.
source to share
I read a good blog by Rick Strall called Simple Business Object Wrapper for LINQ to SQL , which answers some of my questions. He takes some time explaining his views on the framework.
source to share