>When was the last time you tried to use the MSDN library? There is NO sales pitch in the library content. Not a single article is written by sales. And, every article I've looked in the last several years clearly states the version. Search there has greatly improved over that time too. There are lots of articles on past versions too. And it's true, even with VFP. Look at the attached image.
>
>Oh, you want something other than VFP? See attached.
>
>SQL Server? See attached.

Thanks for making my point. You need to know where in that hierarchy of document to look for what you need, and among all the Microsoft's websites, which ones. And there, most of the time, you find what's in the help file already (which is good, because for many ActiveX controls the help file just never registered and since the filenames bore no similarity with the control names, couldn't be found except accidentally).

SSMS is supposed to be one-stop-shop for doing stuff on SQL server. First off, its help menu offers no less than eight choices... and generally offers "help on help", which is an open confession that they made it unnecessarily complicated. I tried a simple, one-word search, and the word is actually a keyword specific to SQL server... first off, it offers (picture 1) a dialog with all other options grayed out (probably because this is Express). Then I get the first result set (picture 2).

Why would SSMS help return, as a top result, a dot net related article? I am coming from SSMS, not VS. Note the mention of "community", "entity network" on the right side, and the "explore" on at least three of the first ten articles. I guess "explore" is a buzzword for "this is a technical article".