Vast majority of my business rules are in the form of DataAnnotations. In the UI, I was using the PropertyStatus controls resulting in appearance similar to SimpleApp demo.
Now that I am in Csla4.0, my UI isshowing a lot of red, the TextBox controls have red borders, there is sliding red - and I mean red, message that pops out when the TextBox is entered, and of course the PropertyStatus is still there.
Meanwhile the SimpleApp, which also has DataAnnotations on the Name Property, and a PropertyStatus in UI is showing only the PropertyStatus.
I would like to standardize my UI on a single behavior. Is there a way to turn one or the other on/off. Is there some guidance as to which is more in fashion these days? Of course the PropertyStatus is of value in many other ways for enabling and disabling controls.
This is because you are using Silverlight 4, not because you are using CSLA 4.
SL4 has some really nice validation stuff built into the UI. If you are not using warning/info severity rules, you might choose to just use the built-in stuff (I frequently do). In which case you'd just not use PropertyStatus controls.
Or if you want PropertyStatus, then you need to add a clause to each binding expression to turn off the SL4 feature to handle NotifyDataErrorInfo.
For us the decision is relatively simple., we'll use PropertyStatus.
Our users are in our Apps all day, every working day, year after year for decades. For them, SL's system is way overbearing. For example, sticking out a red message saying that data in a field is necessary when the user clicks in/tabs into a textbox is not very polite and will get old very quickly. I can hear our users screaming, "Why do you think I tabbed into this field - you moron - you don't have to tell me this is necessary every single time!" SL system is great for survey forms, etc. where user will fill out a form once.
More importantly, Csla community has been clamouring for warning/info serverity rule system for years. I am looking forward to putting this capability to some good use. Also, I am not sure SL's system work (may be it will - I just don't know) in situations where you have more complex rules involving multiple properties and their interaction with each other.
The SL4 feature does integrate smoothly with the CSLA rules system, so multi-property rules should work fine. The primary thing you lose is the severity concept, and the PropertyStatus look and feel.
I too am interested in this. It's acceptable if your form has a few controls but if it's already busy with 30 or more controls then this 'feature' with red highlights do make too much noise. Unfortunately I'm putting all my resources into getting up and running with Sivlerlight at the moment and can't put any time to solve this one....I would be very interested (I'm sure others will be as well) if you find a good workable solution. Keep up posted please.
Copyright (c) Marimer LLC