add new issue       

Issue ID:  623     Rename ValidationRules to BusinessRules and add business rule delegate      
Created by rocky on 2009-10-27 10:38 AM, 3041 days ago
Project:  CSLA .NET
Category:  enhancement
Priority:  high
Status:  closed
Feature area:Validation
  Entering "issue#999" in comment creates link to id 999

show inline images      show change history

comment 2330 posted by rocky on 2010-04-01 12:00 PM, 2885 days ago 

Most work on this item is now complete.

The primary remaining issue is to enable "rule sets" - different rule managers based on some contextual value.

comment 2217 posted by rocky on 2010-02-26 1:02 PM, 2919 days ago 
merged bug 459 into this bug:
Allow adding a list of RuleMethod objects to a new ValidationRules.AddRules() method
comment 2216 posted by rocky on 2010-02-26 1:01 PM, 2919 days ago 
merged bug 430 into this bug:
Add overload to AddRule() to accept a lambda expression
comment 1993 posted by rocky on 2010-01-10 3:58 PM, 2966 days ago 
merged bug 17 into this bug:
Add an attribute that can be used to decorate rule methods to make them discoverable by external tools (like code generators)
comment 1973 posted by rocky on 2010-01-05 10:57 AM, 2971 days ago
comment 1899 posted by rocky on 2009-11-21 12:20 AM, 3016 days ago 
Generally do this list of things:
comment 1789 posted by rocky on 2009-10-27 10:38 AM, 3041 days ago 
Rework the business/validation rules subsystem to match the way it is really used.

Which is to say the ValidationRules property should be renamed to BusinessRules, and there should be a business rule delegate that returns void to compliment the validation rule delegate that returns bool.

Or even consider changing the validation rule delegate to return void and get the result back via the args parameter (though that would mean creating a different args parameter per rule invocation).
comment 1413 posted by rocky on 2009-07-28 2:51 PM, 3132 days ago
comment 1327 posted by rocky on 2009-06-25 8:37 AM, 3165 days ago