Visual Studio help-launcher rant
Yes, I know I am far from the first to bemoan the atrocious behavior of Visual Studio 2005 when you press the F1 button, even accidently. The first time you do it - or other times, if it deems the contents sufficiently changed for some reason - you are treated to an obnoxious and uncancellable dialog saying Help is updating itself and showing an uninformative neverending progress bar.
Worse yet, this window, despite being non-modal (due to running in a different process, dexplorer.exe) still blocks the calling thread on devenv.exe, preventing me from working for up to 5 minutes(!) at a time. No Abort button, no way to tell it to skip this pointless operation - launching help from VS is simply a giant waste of time.
What I now discovered is that I can't even use the task manager to kill the dexplore.exe process, because Visual Studio actively monitors it and RELAUNCHES it, apparently from scratch, if I try to do so.
So tell me, what program manager decided that this particular feature, launching the Help window in a completely different process, was so amazingly important that it was allowed to take over my Visual Studio completely for whole minute while I just sat there and twiddled my thumbs?
Tools -> Customize -> Keyboard -> Show Commands Containing -> Help.F1Help -> Remove.
There. F1 is disabled. Peace is resumed.