Sometimes you're navigating in the MSDN Library and you spot an error in the documentation. You decide to send your feedback and you might wonder if someone reads your comments. Yes, we do! And we take them very seriously!
From small typos to missing code samples to more serious errors, we analyze the comments and make the changes as possible.
One example of a topic that was changed based on the user feedback was the reference for the GridView.RowEditing event. Some of the comments were asking for examples of how to use this event when you are setting the data source programatically and not using the DataSourceID property. So, in the new release of the documentation we added a new sample to the property with the comments in mind.
You can compare the new version with the previous one!
But, for us, it's also important that you give us positive feedbacks when you find useful topics. This helps us track when we're doing it right as well and use that as a model to be followed!
PingBack from http://microsoftnews.askpcdoc.com/documentation/the-power-of-your-feedback
Hello Maira,
I've found this post and your blog because Andrew Pardoe mentioned it here:-
http://blogs.msdn.com/clrteam/archive/2009/02/19/why-catch-exception-empty-catch-is-bad.aspx
He says "I'm pretty sure that text entered in the feedback box ends up as a bug in her bug database so this may be more efficient than using Connect".
Having ignored the "Feedback" link before, and been wary that the feedback gets lost in Tumbolia, I've decided to test his assertion. I've just given feedback that the docs for this method:-
http://msdn.microsoft.com/en-us/library/dw229a22.aspx
don't list all the exceptions that the method can throw.
I wonder if, after a few days, you can confirm that the bug has appeared in your database? Thanks.
Hi Andrew,
Yes, that is correct. We have a database for all customer feedback provided online or via SDK.
I manage the CLR documentation team, but I'll keep an eye for the one you mentioned. Probably next week I can find it there.
Keep in mind that we receive thousands of feedback, so when customers provide feedback it might take a while to see the changes and the change will only be applied to the latest version.
A few more examples where we incorporated customer feedback into our docs:
- http://msdn.microsoft.com/en-us/library/system.text.regularexpressions.regex.escape.aspx
- http://msdn.microsoft.com/en-us/library/ms149397.aspx
If you go to these topics, you can look for two things:
1. On the top of the page there is a freshness date indicating the last time this topic was updated for topics that were changed after the last release.
2. On the bottom of the page, there is a Change History table indicating what was changed and the reason for it. You'll see that most of the times, the reason is customer feedback.
So take advantage of this communication channel and let us know where we can improve.
Thanks,
Maíra
Andrew,
I see your comment for the http://msdn.microsoft.com/en-us/library/dw229a22.aspx topic in our database. You mention that the corresponding Load method has the exceptions listed. I'll follow up with the writer of this content to see if we can get this updated.
Thanks for your feedback.
Maira
Great; it works!
I'll try and comment each time I find a method that's underdocumented re. exceptions.
Andrew