Instead of doing lots of customer research to generate the "How do
I"'s, why not just improve the search? This is only going to be of
limited use. The moment that the thing you want to do is not in the
"How do I" list, and you don't know the whole API off by heart, you're
stuck with trying the Search, which, let's face it, sux big-time.
Your search needs to be as good (or close to) as Google.
MSDN search is poor. It was poor 5 years ago, it looks worse now.
There was an earlier post - about how some developers "know the API"
and some don't, and the MSDN/VS search was geared towards the ones who
do.
I took real exception to this, probably because I'm in the group of
people who don't know every API in MSDN that I want to use. But seriously? What a
crock! Basically, you're saying that the current search is so poor that only
people who don't really need to use it will find it useful??
Another thing - it's not just the MSDN/VS help that's poor - it's also Winhelp.