We're very disappointed to discover that F1 Help in VS2008 is still not
context sensitive.

This used to work fine in VS2003 but was broken in VS2005 and still occurs
in Visual Studio 2008 RTM. It is the most annoying thing about Visual Studio
(an otherwise fantastic package) and it's even more annoying that it's been
like this since VS2005 (if not before, but at least in the past we could set
MSDN Library to filter things; since it gained online-search capability
(which by the way is fairly useless; I can use a web browser myself if the
local help lacks information) we had the ability to filter the index and F1
help taken away from us. Argh!)

Presumably Visual Studio is still written in C++ so how on Earth is it
possible that this doesn't send crazy the very people making the product and
in a position to fix it?

Pressing F1 and being taken to a place abotu some random object, often in a
framework, platform, or language, I am not using and never want to use,
drives me crazy. You might as well remove the feature entirely. Just make F1
put the name of whatever is under the cursor in the clipboard and we can
search MSDN or the web ourselves, because that's all the feature gives us
right now.

The IDE knows what the function is. It knows what language I'm using. It can
find a definition of the function via Intellisense, yet F1 takes me to
whatever comes first with the same unqualified name and there is nothing we
can do about it. This is beyond a joke.

Sorry if this all sounds a bit harsh but, well, it's been YEARS now and this
is a glaring issue.

Regards,
Jonathan Potter
GP Software