tag:blogger.com,1999:blog-2959448197005916848.post8660556083179384821..comments2011-12-31T00:46:50.361-08:00Ning Zhanghttp://www.blogger.com/profile/04032938658341724797noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2959448197005916848.post-90736543521117151602010-08-03T13:58:00.181-07:002010-08-03T13:58:00.181-07:00Ning<br />I am a sipmle user of applications. Your explanation is quite simple and clear that even being a newbie I feel that I understood something.Sharkyhttp://plumbingsupplieslist.comnoreply@blogger.comtag:blogger.com,1999:blog-2959448197005916848.post-1039624006456655532008-11-15T08:59:00.000-08:002008-11-15T08:59:00.000-08:00Hi Joan, <BR/><BR/>Thanks for the compliment. For Boolean properties, the property system and CLR have already done the validation (meaning the right type cast should never fail), but you may still need to provide your own coercion logic, like a control's IsSelectable property might be affected by its IsActive property. <BR/><BR/>Thanks, <BR/><BR/>NingNing Zhanghttp://www.blogger.com/profile/04032938658341724797noreply@blogger.comtag:blogger.com,1999:blog-2959448197005916848.post-22148440876471142812008-11-13T04:28:00.000-08:002008-11-13T04:28:00.000-08:00Ning,<BR/><BR/>Thanks, great post! - I was wondering what your thoughts were on whether validation and coercion methods are necessary for boolean properties? A failed cast of the new value in the callback would be enough wouldn't it?Joan Mirohttp://joanmiro.blogspot.comnoreply@blogger.com