I wrote an article a ways back about how help files have gotten worse and worse over time. People/companies have attempted automate the generation of help content of many years. Instead of paying a group of college degree'd English majors working as technical
writers and editors to compose organized and purposefully written help references, help files are now built from a mix of source code comments and observable meta data. The result IMO is a huge mess.
Case in point, the new Visual Studio help system. Microsoft's again has shifted to an even more automate help system, and this time the results reach a new low watermark. The new Visual Studio help system removes the document explorer and (if you decide to use local help) switches to a locally hosted web server, displaying help in your default web browser.
What's the problem with this? Well in addition to losing dynamic help, the help index, and the expandable help tree, you can no longer search the help effectively. What do I mean by effectively? Suppose you want to read about a type List<T> ... you have to go to the web page, move to the search field, type List<T>, press search, and you are then presented with a paginated list of results, none of which match your search criteria. Why? Because the new search system requires an exact match to get you the results you need, and without an index it's difficult to know what are the exact matches.
Also, there is no more filtering, so when I do a search for "List" I get this:
Awful, awful, awful