CSLA:
The location of choice to learn about this technique is Rocky Lohtka's CSLA site. There is also more descriptive information on wikipedia.
It is not easy, but we are (even at this early stage) able to see the potential for making an investment on architecture that offers a logical separation of application layers (UI, UI-Control, Business, Data Access, and Database) that can be deployed in a multiple variety of physical configurations.
The links offered at the top of this page are a great start. There are also a variety of videos on YouTube where the author of CSLA discusses some of its aspects. One interesting aspect of CSLA is the vibrant and helpful user community. It is very supportive. You can take a tour of that community at the CSLA user group forums site.
If this is interesting to you, our recommendation is to really understand the software development principles that CSLA is designed to solve. Rocky himself warns that this is not for everybody or that it should be taken as the last word on SDLC. The first e-book (Using CSLA 4 - CLSA.NET Overview) is a great starting point (specially chapters 2 and 3). In there, Rocky describes the philosophical foundation and makes the case for CSLA. For more information on how to get started with CSLA, please, follow this link.
If this is something you choose to investigate further, you can download the CSLA libraries here. One word of caution (and a mistake we made) is that if you do not have a perfect understanding of .NET 4.0 and higher features (i.e. how to use generic types, XAML, binding, WPF, SL, LINQ, Entity Framework, WCF, Unit Testing, among others), just downloading the code and start learning CSLA by looking at code examples will be a hard, frustrating, and steep road to manage. After trying it that way for a couple of weeks and getting no-where-fast, we decided to purchase a copy of the learning materials and have experienced much more success in learning and taking the steps implementing this.
The location of choice to learn about this technique is Rocky Lohtka's CSLA site. There is also more descriptive information on wikipedia.
It is not easy, but we are (even at this early stage) able to see the potential for making an investment on architecture that offers a logical separation of application layers (UI, UI-Control, Business, Data Access, and Database) that can be deployed in a multiple variety of physical configurations.
The links offered at the top of this page are a great start. There are also a variety of videos on YouTube where the author of CSLA discusses some of its aspects. One interesting aspect of CSLA is the vibrant and helpful user community. It is very supportive. You can take a tour of that community at the CSLA user group forums site.
If this is interesting to you, our recommendation is to really understand the software development principles that CSLA is designed to solve. Rocky himself warns that this is not for everybody or that it should be taken as the last word on SDLC. The first e-book (Using CSLA 4 - CLSA.NET Overview) is a great starting point (specially chapters 2 and 3). In there, Rocky describes the philosophical foundation and makes the case for CSLA. For more information on how to get started with CSLA, please, follow this link.
If this is something you choose to investigate further, you can download the CSLA libraries here. One word of caution (and a mistake we made) is that if you do not have a perfect understanding of .NET 4.0 and higher features (i.e. how to use generic types, XAML, binding, WPF, SL, LINQ, Entity Framework, WCF, Unit Testing, among others), just downloading the code and start learning CSLA by looking at code examples will be a hard, frustrating, and steep road to manage. After trying it that way for a couple of weeks and getting no-where-fast, we decided to purchase a copy of the learning materials and have experienced much more success in learning and taking the steps implementing this.
No comments:
Post a Comment