boo posted on Thursday, November 15, 2007
I think it is prudent of all CSLA developers who understand the power and the purpose of CSLA to go to the below link and read it and make comments. As seen there are many developers out there who continue to think putting rules everywhere (across layers), providing little to no reusability, is okay, because it's a sactioned Microsoft idea. I think many of us spend many hours, days, weeks, months, trying to convince junior developers, managers, directors of the power of CSLA - I know I have - and a lot of times it falls upon deaf ears because people have been so brain-washed into a way of thinking that is not always correct.
As we all can agree, there are good things in patterns, but to those who don't understand them they are a dangerous thing. There was one post copied below that particularly out-raged me. When Microsoft endorses a certain pattern without giving the practices for how to use them and how not to use them it leaves us, developers who are pragmatic, business application developers left inheriting messes created by other people.
Here's the blog:
http://weblogs.asp.net/scottgu/archive/2007/11/13/asp-net-mvc-framework-part-1.aspx
....As for data entry validation and security and whatnot though, I still
put the responsibility for this on the controller, as this is
presentation logic, not business logic....
Notice that not only does this person have the purpose of the controller highly confused, it blantantly wrong in saying that security is the responsibility of the presentation logic. Obviously to him security such as 'allow add', 'allow delete', etc is based upon what pages you can get to and if someone were to hit the back end model they'd have feast of opportunity to do whatever the heck they want because there's no security (or data validation).
Don't let people like this spoil it for the rest of us!
