Source code checked in, #d22b5b57c38a
Ensure CustomizeValidatorAttribute only applies to a single binding context
View ArticleSource code checked in, #334e89aff2d6
Support rules for nested properties at the top level (without needing to specify a child validator)
View ArticleSource code checked in, #50879832092a
Ensure DefaultPropertyNameResolver returns null if the expression couldn't be converted to a string.
View ArticleSource code checked in, #88c56967e156
Add support for inferring display name from DisplayAttribute and DisplayNameAttribute
View ArticleSource code checked in, #91849d11e313
Rename PropertyRule.PropertyDescription to PropertyRule.GetDisplayName()
View ArticleSource code checked in, #7bc523c18298
Support DisplayAttribute for SL4 (not supported for WP7)
View ArticleSource code checked in, #baf12e822b9c
Workaround issue caused by referencing DataAnnotations in windows client projects (eg WPF). Does not affect web projects/silverlight.
View ArticleSource code checked in, #f3e229933050
Temporarily remove reference to System.ComponentModel.DataAnnotations
View ArticleSource code checked in, #453bf995342c
Temporarily remove System.ComponentModel.DataAnnotations from Silverlight project for consistency
View ArticleSource code checked in, #43bb1f06ebe2
Introduce top-level Unless method. Remove SharedConditionRuleBuilder.
View ArticleSource code checked in, #78449b4345bc
Remove PropertySelector in favour of standard System.Func.
View ArticleSource code checked in, #da6e799ea2f8
Fixed issue #7084 (NotEmptyValidator does not work with EntityCollection<T>)
View ArticleSource code checked in, #a71a8587b230
Fixed issue #7087 (AbstractValidator.Custom ignores RuleSets and always runs)
View Article
