No way CSLA.NET is "awesome" by any measure. See [1], for example
So we'd just write "around" the abstractions to avoid having to interact with the CSLA "magic".
Eventually I think it was written out of the solution.
CSLA.NET has a lot of really bad parts. I've had to maintain apps written in it and have felt the pain.
Who really changes from a 2-tier to 3-tier architecture anyway? I feel it was only ever popular because of the business objects book.
1) Designed for big projects
2) Easy to screw up without lots of experience
The fact that big projects require many developers means those developers rarely have the experience necessary (with CSLA - even an experienced .NET developer is at a disadvantage) to architect it properly, and so it becomes a maintenance nightmare.It's instructive (for business app developers, anyway) to read Rocky Lhotka's book in order to understand what problems he was trying to solve with CSLA, but it's not really worth using the framework...