i am somewhat less inflamed about this one, as i know it is difficult to produce good docs, and there is evidence that ms makes a big effort to do so. that is appreciated. but what is problematic, i think, is the adoption of a certain 'style'. The aim is generally to be 'correct' rather than informative, in most of the documentation. you must understand that your development frameworks have now got many, many layers to them, and i don't think anyone in the world could possibly be familiar with even 1/2 of 1% of it.
The key i think is to adopt the style of 3rd party software book writers, who approach each topic first by a careful introduction where there is, to the degree possible, and effort not to assume much familiarity with the area covered, and provision of the necessary building blocks and terminolgy to allow the ready to advance more easily forward into the more complex aspects of the technology. I do eventually find, that after staring at things look enough, stuff in your docs begins to sink in, but it is rather torturous, and again, time consuming in a way that is unnecessary.
Also, references throughout the docs tend to be circular, in the classical manner of a bad dictionary that defines one obscure word in terms of others, and upon looking up the other obscurities, one finds oneself refered back to the original obscurities, with no escape.

Complaint No ??6, or so, DOCUMENTATION IS RATHER BAD
vnavna
GEORGE62
please use this forum for your thoughts about the documentation system in general
http://forums.microsoft.com/MSDN/ShowForum.aspx ForumID=66&SiteID=1