title: Is Asp.Net MVC + CSLA + DDD Possible
body: <p>I was asked to review a system the other day that was based on ASP.NET MVC + CSLA + DDD (domain drive design).  The first version of this system was based on ASP.NET MVC + CSLA.  The second release was based on that plus added DDD.  The reason is because..... well, I don't know what.  As I looked at the diagrams from the two different architectures, it was pretty apparent that the second version was extremely more complex.  The CSLA objects basically used the Domain objects.  When you see something like this you know it already smells but it is hard to justify why someone shouldn't do it this way without A) having extreme knowledge of all topics or B) using it for a long time.  I have neither of these for this topic but I know if I'd built this from scratch I wouldn't have done it this way, nor wouldn't a lot of developers I associate with.  </p>
  
  <p>So, dear reader, what would you do in this situation?  My thoughts are that if you want to use CSLA and MVC and DDD then you make a stand and chose one or another (CSLA or DDD).  If you don't there are too many cooks in the kitchen.  </p>
  
  <p>Please shed some insight if you have opinions on this matter.</p>