Thank.

“Programming the class against the interfaces is elegant for number of reasons. First, as I mentioned, we’re defining the “how” for retrieving the email addresses. (…)”.

IMHO, interfaces define the “what” who implements the interface does, no matter how. The interface implementation defines “how” to do the “what”.

Also, do any of you guys know any mock framework that lets me create partial mock without the need to create interfaces for everything or declaring a method as virtual? It doesn’t seem right to me modifying good code (e.g. creating an unnecessary interface) just to make testing easier.

Thanks in advance

Looking at the documentation of the method, I’ve checked that it works like this

Less than zero (not strictly -1) => smaller
Zero (strictly zero) => equal
Greater than zero (not strictly 1) => bigger

Check the table at http://msdn.microsoft.com/en-us/library/system.icomparable.compareto(VS.71).aspx

Just a minor contribution. Still reading the paper, and liking what I read so far.