Whilst editing a WPF view, the XAML designer claimed it couldn’t display a child user control due to a null reference exception. Looking at the stack trace, I noticed a wonderfully named method…
Just saw this comment on Stack Overflow, and thought it too good not to repost…
A programmer’s wife sends him to the supermarket. She tells him, “Buy a loaf of bread, and if you see some eggs, grab a dozen.”
The programmer later returns with a dozen loaves of bread under his arm
Forget all you ever learnt about enterprise design, I’ll reveal the truth, and it’s not pleasant (but quite funny!)
Following on from my previous posts with great error messages, here are some more
Having blogged recently about some great error messages, I came across another one! Microsoft much employ people to craft these, they just couldn’t be there by accident. I reckon they are put there to amuse developers, and distract them from the fact that the software is misbehaving!
Anyway, I was using the SQL Server Import and Export Wizard, and it threw up the following error message:
Error 0xc004706b: Data Flow Task 3: “Destination 14 – EntityHistory” failed validation and returned validation status “VS_ISBROKEN”
I just love that last bit!
And I’ve seen a few! I was just trying to back up an SQL database, and got this truly wonderful error message… Not much you can say to that is there?
Bored of the usual methods of inflicting torture upon myself, I thought I would upgrade SQL Server 2008 R2 to SQL Server 2014 (stop laughing at the back!), because, erm, well it seemed like a good idea at the time.
Read more to hear the whole sorry story
“I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone.”
Danish computer scientist Bjarne Stroustrup
Of course, we professional programmers never make mistakes, ahem. That’s why we never need to use debuggers, ahem.
Well suspend belief for a moment, and assume that I had a bug in the code I was developing. You know the feeling, you stare at it, you write unit tests, you stare at it some more, and still can’t work out why on earth Visual Studio is claiming that there is an error in your code, when it’s so obvious that there isn’t. You even get to the point of talking to your computer, pointing out the error of its ways…