<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Notes on Software</title>
	<atom:link href="http://softnotes.wordpress.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://softnotes.wordpress.com</link>
	<description></description>
	<lastBuildDate>Thu, 25 Sep 2008 20:10:50 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Validation in WPF with .NET 3.5 SP1 by Using BindingGroup in custom controls &#171; Notes on Software</title>
		<link>http://softnotes.wordpress.com/2008/08/20/validation-in-wpf-with-net-35-sp1/#comment-14</link>
		<dc:creator>Using BindingGroup in custom controls &#171; Notes on Software</dc:creator>
		<pubDate>Thu, 25 Sep 2008 20:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://softnotes.wordpress.com/?p=15#comment-14</guid>
		<description>[...] above fails. But this binding error does not participate in the validation mechanism (look at my earlier post on validation for a pattern for implementing validation). The solution is to find a BindingGroup [...]</description>
		<content:encoded><![CDATA[<p>[...] above fails. But this binding error does not participate in the validation mechanism (look at my earlier post on validation for a pattern for implementing validation). The solution is to find a BindingGroup [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Validation in WPF with .NET 3.5 SP1 by [WPF] Validation des donn&#233;es, du nouveau avec le 3.5 SP1 , Elise's blog</title>
		<link>http://softnotes.wordpress.com/2008/08/20/validation-in-wpf-with-net-35-sp1/#comment-12</link>
		<dc:creator>[WPF] Validation des donn&#233;es, du nouveau avec le 3.5 SP1 , Elise's blog</dc:creator>
		<pubDate>Thu, 11 Sep 2008 15:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://softnotes.wordpress.com/?p=15#comment-12</guid>
		<description>[...] parallèle, un autre blog poste le détail d&#039;une solution de validation des données, toujours en utilisant le BindingGroup  [...]</description>
		<content:encoded><![CDATA[<p>[...] parallèle, un autre blog poste le détail d&#8217;une solution de validation des données, toujours en utilisant le BindingGroup  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Validation in WPF with .NET 3.5 SP1 by K. M.</title>
		<link>http://softnotes.wordpress.com/2008/08/20/validation-in-wpf-with-net-35-sp1/#comment-7</link>
		<dc:creator>K. M.</dc:creator>
		<pubDate>Thu, 21 Aug 2008 20:37:39 +0000</pubDate>
		<guid isPermaLink="false">http://softnotes.wordpress.com/?p=15#comment-7</guid>
		<description>Karl,
I am recommending throwing exceptions &lt;b&gt;only when property level validation logic is violated&lt;/b&gt;, that is when a value is being set that can &lt;b&gt;never&lt;/b&gt; be valid, irrespective of the values of other properties. An example would be when an Age property is set to a negative value. If a value is being set that puts the object in an invalid state because of &lt;b&gt;inter-property&lt;/b&gt; requirements, exceptions &lt;b&gt;should not&lt;/b&gt; be thrown.
Note that I also return null in the IDataErrorInfo indexer. There are no property level errors for IDataErrorInfo to report in my approach. I use IDataErrorInfo for its Error property, which returns all object-level errors. This makes the error logic cleaner. I can put validation logic that depends on three properties at a single place in the Error property instead of thrice in the indexer. 
Hope that makes my reasoning clear.
Thanks for the feedback.

K. M.</description>
		<content:encoded><![CDATA[<p>Karl,<br />
I am recommending throwing exceptions <b>only when property level validation logic is violated</b>, that is when a value is being set that can <b>never</b> be valid, irrespective of the values of other properties. An example would be when an Age property is set to a negative value. If a value is being set that puts the object in an invalid state because of <b>inter-property</b> requirements, exceptions <b>should not</b> be thrown.<br />
Note that I also return null in the IDataErrorInfo indexer. There are no property level errors for IDataErrorInfo to report in my approach. I use IDataErrorInfo for its Error property, which returns all object-level errors. This makes the error logic cleaner. I can put validation logic that depends on three properties at a single place in the Error property instead of thrice in the indexer.<br />
Hope that makes my reasoning clear.<br />
Thanks for the feedback.</p>
<p>K. M.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Validation in WPF with .NET 3.5 SP1 by Karl Shifflett</title>
		<link>http://softnotes.wordpress.com/2008/08/20/validation-in-wpf-with-net-35-sp1/#comment-6</link>
		<dc:creator>Karl Shifflett</dc:creator>
		<pubDate>Thu, 21 Aug 2008 19:39:43 +0000</pubDate>
		<guid isPermaLink="false">http://softnotes.wordpress.com/?p=15#comment-6</guid>
		<description>Why are you recommending throwing exceptions from property setters when your also implementing IDataErrorInfo?

  &quot;Apply property level validation logic in the property setters of the domain objects. Throw exceptions when the logic is violated.&quot;

I have a complete write up on this on my blog at:  http://karlshifflett.wordpress.com/2008/04/20/fort-knox-business-objects-yes-no/

I&#039;m seeing this practice in a number of spaces and really can&#039;t understand why this is being recommended.  

Thanks for you feedback and have a great day,

Karl</description>
		<content:encoded><![CDATA[<p>Why are you recommending throwing exceptions from property setters when your also implementing IDataErrorInfo?</p>
<p>  &#8220;Apply property level validation logic in the property setters of the domain objects. Throw exceptions when the logic is violated.&#8221;</p>
<p>I have a complete write up on this on my blog at:  <a href="http://karlshifflett.wordpress.com/2008/04/20/fort-knox-business-objects-yes-no/" rel="nofollow">http://karlshifflett.wordpress.com/2008/04/20/fort-knox-business-objects-yes-no/</a></p>
<p>I&#8217;m seeing this practice in a number of spaces and really can&#8217;t understand why this is being recommended.  </p>
<p>Thanks for you feedback and have a great day,</p>
<p>Karl</p>
]]></content:encoded>
	</item>
</channel>
</rss>
