Using CSLA as an application framework

I have been using CSLA 2.0.1 for a couple of 2.0 windows applications and thought it was time to share some thoughts.

Pros

1. Object Orientated Programming (OOP): I originally coded .NET in datasets, I now use objects. I made this change when .NET 2.0 was first released as MSFT made many improvements to object binding. I couldn’t go back to implementing a solution using datasets. When designing a solution I find it so much clearer when thinking objects…it comes naturally. CSLA is centered around OOP and generics.
2. Keeps business logic where it should be…in the Object. CSLA takes object encapsulation to a true OO design. The object manages:
   • Authorization: Who can delete/add/update/select an object.
   • Validation: Basic property validation …Required fields, max/min lengths, data types.
   • Business Rules:  Complex business rules validation. Allows you to easily write complex business logic into the object and validate these rules.
   • Data access (this can be removed and put into a data layer if required)
3. Windows development: BindingSource, CSLA Object & ErrorProvider = Zero code for validating controls in UI (Sh*t hot)
4. UI: Due to the object encapsulating much of the functionality, it allows the UI to be dumb. Could easily create a Web UI and Windows UI for any CSLA project that we design. Remember the object validates it properties which bound to controls on the form, takes care of authorization through roles, contains business rules and manages the data access. Not much left for the UI to do
5. All this adds up to easier code maintenance.
6. Community driven: There is a solid community for support, direction and discussions.
7. Code generation: Can easily code gen your objects using Templates and Code Smith (free version 2.6 works fine)
8. Written to support WCF.
9. The framework is FREE.

Cons:

1. Learning curve. As with any new technology/framework there is a skill up period. This needs to be weighed up before deciding to use CSLA. I work for a company (Data Cogs) and we have made the decision to use CSLA for all projects.
2. Can take more development hours than using datasets.
3. I have experienced some minor problems with the code generation templates…but hey, they are free and you can change to suit your requirements.

There are other things that I haven’t discussed as I haven’t used, including one of the main benefits in using CSLA (Component Scalable Logical Architecture) which is built into its name. It allows you to design the same system that can work in both a client/server environment or physical n-tier environment where objects can cross app domains. This was always a huge issue as the design of your system was usually built around its technology/architecture. CSLA apparently takes this decision out of the equation when designing your system.

I would love to hear other peoples views on CSLA…