This error has cost me almost two days to debug:

Its only symptoms where spurious but widespread changes to a single property. While this is “obviously” human error, these “easy” points would have mitigated the damage done:

• strict type checking: the expression is of type string and not of type bool, the C# compiler would have known the difference and issued an error
• in-band evaluation: The expression didn’t trigger breakpoints within the MethodName property. This would have pinpointed the cause of the data change immediately
• constant vigilance!

This entry was posted on Thursday August 20th, 2009 at 04:36 PM and is filed under Microsoft, Tech. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.