Much as I love how helpful everything is in Visual Studio 2005 and the way it just makes everything so much clearer and easier, there are just a few times as will all automated software you just want it to shut up.
One case I sometimes feel this is true is the Exception helper. Though not always, its great when debugging code you know is wrong. But when you've spent half an hour typing and checking and getting rid of every compiler error, to finally run and get a nasty run time exception like this is annoying for two reasons. One is the fact it didn't spot the error a particular type of error until the program was running, and two that it poings up, points at something you've written and goes THIS IS WRONG! I almost feel it should be in red with nasty ink and 'see me after class' at the bottom. Though maybe it should just be reworded to something like this:
One case I sometimes feel this is true is the Exception helper. Though not always, its great when debugging code you know is wrong. But when you've spent half an hour typing and checking and getting rid of every compiler error, to finally run and get a nasty run time exception like this is annoying for two reasons. One is the fact it didn't spot the error a particular type of error until the program was running, and two that it poings up, points at something you've written and goes THIS IS WRONG! I almost feel it should be in red with nasty ink and 'see me after class' at the bottom. Though maybe it should just be reworded to something like this:
- Current Mood:
dorky
Profile
nidonocu- Nidonocuous
- Nidonocu.com
Comments
"...If you know it's missing, why don't you put it in?"
"...Because the day people realise that computers can write code themselves, people will be obsolete."
"...I'll just put that semicolon in, shall I?"
"Yes, you do that."