A group blog from members of the VB team
The documentation team has just released a survey aimed at gathering feedback on Visual Studio content. Are you dying to tell us what you think about the Visual Studio content in the MSDN library? Please share your perspective by taking part in the Visual Studio Content Survey. The survey is completely anonymous and doesn't require that you fill in any personal information. It should take about 10 minutes to complete.
Visit Kathleen's blog for more information. Thanks for helping us improve our documentation!
Enjoy,-Beth Massi, VS Community
PingBack from http://www.artofbam.com/wordpress/?p=7439
After the 6th or so question every time i hit the next button the survey resets back to the first question.
Thanks Bradley. I checked the survey, but didn't experience the behavior you did. Many people have responded to 90% of the questions (mostly skipping the last "any additional feedback you like to give us?" question); so I'm not sure why this happens for you, but I will look into it further.
Please show an API roadmap for when the different Microsoft APIs become obsolete and how and what parts of win32 will be replaced with a roughly equlvalent .NET api. Visual studio and .NET in general could really use better video, audio, and image processing APIs (i.e., try to open an MPEG2 file and find out how long it is in .NET 2.0). Windows, in general, should add much much better multimedia handling tools (i.e., decent video and audio editing as standard windows programs - mpeg2 files included).
The biggest weakness of Visual Studio and it's programming languages is the documentation.
More is NOT always better.
Microsoft has not improved on book organization (i.e. Table of contents, body, index). Stop trying.
Stop forcing me to go online to actually find anything. I often work unconnected. Making me go to online communities is a cheap, cowardly, abdication of responsibility for clear coherent documentation of your product.
As for most of the content, the *first* things I ALWAYS need to see are:
1) A minimal high level explanation.
2) The SIMPLEST possible code sample, demonstrating its use.
3) Another code sample explaining common uses.
In production environments, I would love to, but don't usually have time to, examine the minutia of an object's properties or member functions. I have to get the work out. Please, please, please write documentation to make THAT task the highest priority, while making more complex tasks possible.
Agreed. Do not force me to go online to get documentation. I search documentation in this order:
1. local msdn (full install of all documentation/samples from dvd)
2. usenet groups (see below) - microsoft.public.dotnet.languages.csharp
4. web search engine
Usenet groups for .net are the single best place to search for a particular api call. It's much faster since they are text, are retained (10+ years), and don't require a registration or purchase. Requiring registration is a major annoyances since much of the internet content parrots the MSDN page or is stale from the 1.1 .net framework.
I usually search the CSharp usenet newsgroup first, followed by the VB group and then by the .NET group subtree.
General web search is last because many of the web pages, blogs, etc. just parrot the MSDN sample.