Why MSDN tech resources/documentation fails

Question

Hope this is the right forum to post this, hard to tell with over 300+ forums to select from.

I've finally pinpointed what is seriously lacking in Microsoft's documentation including online MSDN resources:

1.  It's "why".  That question is never answered, "Why do I want to user this property or method?"  Provide a meaningful context of why any particular property or method or class is used and/or available for use.  Typical usage.

2.  Context tree on sample code that would provide a means to narrow down or back up thru what the sample is trying to accomplish.

3.  Understand my source context when I hit the F1 help key -- when I hit the F1 key in VS 2008 it knows I'm working on a Windows Forms project in VB using .NET 3.5, but I'll get endless listing of C#, Java, ASP.NET, etc. etc.  after wading thru the junk I don't need I might get a hint of what I actually want.

4.  Community Content is almost ALWAYS empty, yet I know I see many related posts on MSDN forums, why are this not linked in?

Often makes me wonder if Microsoft really does want to encourage software development for their OS/platforms.

Rob