2007-06-27 03:37:37.017185+00 by Dan Lyke 6 comments
More software hate: The shortcut for "Build->Build Solution" in Microsoft Visual C# 2005 Express Edition is F6. The shortcut for "Build->Build Solution" in Microsoft Visual C++ 2005 Express Edition? F7.
[ related topics: Humor Microsoft Software Engineering moron ]
comments in ascending chronological order (reverse):
#Comment Re: made: 2007-06-27 15:45:05.673355+00 by: mvandewettering
I hate the abstraction too: what the f*ck is a "solution" anyway?
#Comment Re: made: 2007-06-27 16:52:35.947588+00 by: Dan Lyke
I'm not even going there... Anything that runs on Windows is, at best, a stopgap, not a solution.
#Comment Re: made: 2007-06-27 22:35:38.192818+00 by: Dave Goodman
Back in the CP/M days keyboards all had the arrow keys in different places, and they sent different codes to the computer, and the editors all used different control codes, and there were no Function keys. "F6 is now F7," you say? Suck it up, and stop sniveling! ;)
#Comment Re: made: 2007-06-28 02:35:02.913448+00 by: Dan Lyke
Aaargh!
"Build->Build Project"
"Build succeeded"
"Debug->Start Debugging"
"There were build errors. Would you like to continue and run the last successful build?"
Okay, look down and see that, allegedly, "No overload method for 'DoPointerDown' takes '6' arguments. Realize that in that external DLL, perhaps I have two classes which define "DoPointerDown", and one of them only takes two arguments, maybe it's getting the wrong class definition? Rename that method, but noooo... And the context sensitive help in the editor still tells me it takes 6 arguments.
#Comment Re: made: 2007-06-28 10:39:10.198794+00 by: meuon
Context sensitive help in the editor? Weenie. :)
#Comment Re: made: 2007-06-29 02:51:52.255226+00 by: Dan Lyke
You've got to have context sensitive help, to keep up with all of the stupidity of the APIs that Microsoft publishes.
Hate of the moment: In most modern debuggers you can inspect structures and even call const members and functions on objects. I'm trying to look at the contents of a boost::shared_ptr<...> right now, because the debugger is breaking at a location and not telling me why, and it won't let me.
Sigh.