<p>The main web application of my company is crying out for a nifty set of libraries to make it in some way maintainable and scalable, and one of my colleagues has suggested CSLA. So I've bought the book but as :</p>

<blockquote>
  <p><em>programmers don't read books anymore</em></p>
</blockquote>

<p>I wanted to gauge the SOFlow community's opinion of it.</p>

<p>So here are my questions:</p>

<ol>
<li>How may people are using CSLA?</li>
<li>What are the pros and cons?</li>
<li>Does CSLA really not fit in with TDD?</li>
<li>What are my alternatives?</li>
<li>If you have stopped using it or decided against why?</li>
</ol>

We started using CSLA because we thought it would help with our model layer.  Was sort of overkill and mostly all we use now is the SmartDate class, just because we're already linked to the library.
We thought the validation interface would really help us enforce business rules but it didn't work well with WCF and serialization (we're still stuck on version 2.0.3.0, so things might have changed).