Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.
Sign up to join this community
Downvote if you Don't Agree that we should ban questions whose answers that are searchable on the Net.
The intention of this question is make it very clear that we should not be rude about developers whose questions can be found on MSDN, Google, or a book.
Should we ban all C# Questions whose answers are already in MSDN?
You can't assume that the people posting the question didn't do a search. If they got the search term slightly wrong then then there's a good chance that they wouldn't see the result in the MSDN.
Also even if the answer is in the MSDN, it's not the easiest of sites to navigate and find information from. I often have to search through several pages following multiple links to get the information I actually need. So having an answer that deep links to the relevant MSDN page is a good thing.
The "problem" here is those people who leave such comments. They're not constructive and are often rude. If you (not you, but the commentators) don't want to answer the question then just don't answer the question. Move onto something more "worthy" of your time.
In short, no.
To add to Chris's answer, MSDN is a fairly good resource and reasonably well indexed by Google. However, despite having topic pages for much of the .NET Framework, its languages and many other things, many of these documentation pages don't have good examples of how to use a particular feature or class library.
It may also be non-obvious to a learner how groups of features documented across several (and often unrelated) pages can work together to arrive at a solution.
For example, say you're a developer working with the IIS7 administration API's:
http://msdn.microsoft.com/en-us/library/ms692515(v=VS.90).aspx
The docs there amount to some waffle about how these API's enable developers to extend and manage IIS7 and then a huge blob of rather terse descriptions of the API's themselves. There's not much context and the reader may not know they also need to browse over to here to provide some background for these API's and their usage.
I've been using MSDN in its various forms (offline and online) for 14 years and there are still days when I find myself tearing my hair out when trying to piece together information on how to use a particular API or language feature.
Sometimes you need assistance with understanding the documentation and that's a fair enough thing to ask for.
