really hating the new help

Question

How close is beta 2's help to to being what we'll see in the final? In my short experience with it, it's almost useless. For example, when I directly type in class names, like "List<T>", I don't get a single result on the first page for the framework's List<T> class.

Also- I only get 10 results per page, will this be configurable?

In addition, the results aren't categorized-- for "List class", I get stuff from the STL, the XAML, mobile controls, etc. The old help would bother to ask me what I'm looking for, this one just throws a wad of "maybes" at me and forces me to wade through them all. Is this going to change?

If this is at all representative of what we're going to see in the final, I'm very sad to see this devolution.

--
If this has been discussed, kindly point me to it, since searching "help" and "help system", etc, got me nowhere.

Answer 1

When you're using the new Help, do you mean the pages that open in a web browser? If so, I agree with you that I *really* really hate the new Help. I much prefer the local help being available in a standalone viewer (dexplore.exe). I like being able to drill-down and still see the full tree hierarchy. The web browser version lacks that ability.

Chuck

Answer 2

Mine didn't work at all until I followed the directions here (probably due to old betas)

http://blogs.msdn.com/help3team/archive/2009/10/21/how-to-repair-a-help-viewer-help-3-beta-2-installation.aspx

in step 11 - I reinstalled the offline help by pointing to the "ProductDocumentation" folder from the DVD and choosing the helpcontentsetup file.

The best description I've found of the internals of the help system is found here:

http://www.helpware.net/mshelp3/intro.htm

I cannot find the "Index" tab anywhere?  I only see table of contents and a simple search box (with no options). An Index is a must.  Where are the search options located?  (i.e. VC2008 - Language/Technology/Content type).  Also the "Filter" dropdown in the Contents tab.  These are a must.

Can you tell me when these features will be delivered? e.g. interim CTPs etc?

Answer 3

I agree.  If this is close to final, it seems like a step backward in a number of ways.

1.  It uses an ordinary Internet Explorer window.  While Internet Explorer is up to this task, it causes the desktop to consolidate the help browser with the half dozen other Internet Explorer windows that I have open at the time (or in Windows 7 into the single Internet Explorer button).  I loved how Document Explorer stayed separate, with its own title and icon.  To be fair, this behavior can be "blamed" on other components of the system, but that doesn't make it better for me.

2.  As others have said, where is the index button?  This is helpful for finding things when you are not quite sure what you are looking for.

3.  The Search box is useful (and quite important given the lack of the index button).  In fact, it is usually better than the Index button (great!).  But I have found some weaknesses.  For example:

* Typing "Console Members" brings up two exact matches with no indication to help me pick one.  This of course is because there are two Console classes but the search page doesn't let me see which one is which.

* Typing "System.Diag*" fails to bring up "System.Diagnostics Namespace".  It only brings up a CodeAnalysis namespace.

4.  Clicking any node in the table of contents automatically collapses the previously expanded node and navigates to a new page immediately.  I'd prefer an "AJAX" table of contents that I can browse through before commiting to another node.

5.  Overall, the new help seems to force the user to do things its limited way instead of allowing users to take advantage of help browsing techiques that emerged through years of experience with the old local MSDN help systems.  There are a lot of good things about the new system.  I like how the web and local will have the same features, and the search box is powerful when used correctly.  But overall I just not having fun with the new help system!

I do hope some improvements are made to the help browser.  To the original poster, I'd recommend experimenting with the search box.  Here are some sample inputs that I have found to work well:
  Console Class
  Console Members
  Console.ReadLine
  Console.Read* (notice the wildcard)

Answer 4

Sadly, it appears that Microsoft have indeed lost their minds and intend to ship offline help without an index: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=505032

What do they think offline help is for? If I want search I use Google, it is much faster and much more accurate than the built in search anyway. The only reason for the existence of offline help was for the index, and now they are taking it away.

---

Moderator | MCTS .NET 2.0 Web Applications | My Blog: http://www.commongenius.com

Answer 5

Well, at least your bug hasn't been closed. As I said in my comment there, I don't understand whether they're implying it'll be fixed up somewhat for future betas or the RTM version. Still, with 9 importance votes and a bunch of comments in agreement, maybe we'll see some improvment...

I'm glad I found this thread, I was coming to ask/moan about the help system myself. My major problem is that I can't view a help page as a tabbed document within the IDE. I always use two column tab groups, so I can see two bits of code at once, and if I'm looking at some docs for an area of code I'm working on I always display that in the other tab group. That way I can read it and look at my code at the same time, all in once maximised IDE. Opening in my browser means hopping back and forth all the time, I hate it! Plus the assumption everyone "searches" first is just wrong; I always use the index and contents panes, because when I search I worry I'll miss something. I also often know exactly what I'm looking for and want to go straight to it, without being carried somewhere else by a wayward search hit.