The hunt for the cause of an error

Like running around the house for 30 minutes trying to locate something just to discover that its been in your hands the whole time, searching for the cause of an error can slow down the creation process to the point of almost derailing the entire flow and will often burst a whole lot of energy.

My favorite?  Comparing various custom controls back and forth and not seeing any issue at all… eventually realizing the 1 thing missing was a # before a color definition.  What’s worse is when you’re in limbo working in blend where you’ve not transfered everything to app.xaml yet and still are working on that, but can’t go further to make sure you didn’t break anything until you can locate the issue that’s right there in front of you but somehow being blind to it.

UGH!

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: