CSLA 4.0 Implementation - Update #4

CSLA:
The location of choice to learn about this ​technique is Rocky Lohtka's CSLA site. There is also more descriptive information on wikipedia.

CSLA 4.0 Implementation - Update #3

As it is with any new technology, there is a ramp-up time to get proficient at it.
So far, the skill (learning C#) I was expecting to take me a long time to feel "semi-productive" with has taken a lot less time than I had anticipated. The skill (MVVM implementation) I thought was going to be easier to acquire has taken me longer. I'll go through each of the technologies I had to deal with in this journey and come back to this post to add or clarify certain items.

CSLA 4.0 Implementation - Update #2

This post contains a list of resources that can help with the learning curve for adoption of CSLA 4.0. It is based on the items listed on Update #1. I will continue to add resources to this list as I come across them.

Our CSLA 4.0 Implementation - Update #1

During the first third of 2013 I learned a lot about CSLA. Most importantly, during that time I realized how much is there to know about this framework.

1. It is not just an ORM tool. It is a framework for developing Business objects based on an Object Oriented Analysis and Design approach (i.e. object-oriented application vs data-driven application).
2. It has a learning curve, but it is worth the investment in it.
3. It follows 4 "simple" steps:

Story about implementing CSLA in our IT shop

For the past couple of weeks we've been doing a "deep-dive" research on CSLA 4.0 and what it can do.
Just to give a backdrop context, at my place of work, we have implemented a flavor of the CSLA.NET 1.0-ish release (back in the early 2000's).  It has been stripped of many of its original components (i.e. Remoting, DataPortal, among others).  Our CSLA "flavor", has been mainly used as an ORM (object - relational mapper) framework not as a business object framework. Many of the teams consuming the framework have opted for using the CRUD mechanism. Very few take advantage of the n-level undo, the broken rules capabilities, or the use of more complex object graphs and business functionality. We have journeyed through our development cycles under those conditions without rocking the proverbial boat too much during that time.