Answered by:
Where to report erroneous MSDN Library content?

Question
-
I've recently (~a month ago or more) reported several content errors in various MSDN Library pages via the Feedback link on the bottom of the page. However I've seen no changes in any of the pages I've commented on. (Very simple things like typos in property names and invalid default values, so I'm sure they really are errors.)
Is there a proper place to report these errors? Or do I just have to wait longer? Does the feedback I send ever actually reach anyone who has the means to fix these errors? (I've had bad experiences using these "feedback" buttons on Microsoft pages..)
I've found this forum (MSDN, TechNet and Expression Library Feedback), but the description suggests they want feedback on the actual library software (also it's FULL of off-topic posts, so I'm afraid to post there.)
Friday, September 16, 2011 9:18 AM
Answers
-
For other topics I'm not sure. You can leave a comment in MSDN directly...
I read this FAQ and it states that:
"Don’t ask questions or report bugs in the Community Content section."
Later:
"It’s fine to note relevant documentation or product bugs in the Community Content section; however, Microsoft people won’t be reviewing the community content to gather bug reports."
and:
"..file a bug on the Microsoft Connect website."
So I guess Microsoft Connect is the way to go... Though it somehow doesn't feel like the right place to report MSDN Library documentation errors.
Sunday, September 18, 2011 11:40 AM
All replies
-
For SQL Server documentation problems you can use this forum
http://social.msdn.microsoft.com/Forums/en-US/sqldocumentation/threads
Gail Erikson from MS is quite responsive.
For other topics I'm not sure. You can leave a comment in MSDN directly...
For every expert, there is an equal and opposite expert. - Becker's Law
My blogFriday, September 16, 2011 8:39 PM -
For other topics I'm not sure. You can leave a comment in MSDN directly...
I read this FAQ and it states that:
"Don’t ask questions or report bugs in the Community Content section."
Later:
"It’s fine to note relevant documentation or product bugs in the Community Content section; however, Microsoft people won’t be reviewing the community content to gather bug reports."
and:
"..file a bug on the Microsoft Connect website."
So I guess Microsoft Connect is the way to go... Though it somehow doesn't feel like the right place to report MSDN Library documentation errors.
Sunday, September 18, 2011 11:40 AM -
If forum's moderators will chime in in the thread and let us know the proper way, it will be great.
For every expert, there is an equal and opposite expert. - Becker's Law
My blogSunday, September 18, 2011 1:22 PM -
Well, it looks like even the admins don't know a definitive answer to this or just don't care to comment on it. I'll just mark this answered and report back if I ever get a reaction from the people at Microsoft Connect.
Friday, September 23, 2011 7:58 AM -
Did you create any Connect item? If so, can you point me to them?
For every expert, there is an equal and opposite expert. - Becker's Law
My blogThursday, November 1, 2012 5:46 PM -
Did you create any Connect item? If so, can you point me to them?
Sure.
and
https://connect.microsoft.com/VisualStudio/feedback/details/726335/chart-controls-more-msdn-library-documentation-errors
I never reported back since none of the 15 issues I reported have been fixed. (With the exception of DoughnutRadius which was fixed through a separate Connect issue)
Friday, November 2, 2012 11:17 AM