Tuesday, November 14, 2006 5:12 PMModeratorWe've had some confusion about what expectations you should have with respect to the MSDN forums. This thread is an attempt to clarify that confusion, at least as far as how the folks from Visual Studio Debugger Team interact with you here in the forums.Q: What is the VS Debugger team's goal for the MSDN Forums?A: The forums provide a community-driven mechanism by which customers can have questions answered about the Visual Studio Debugger. In addition, they are a feedback mechanism for the product, the product documentation, and product-related activities. Product group members, Customer Support Services personnel, and MVPs will respond to questions here, but we also hope that the community becomes self-sustaining, and that users of Visual Studio can help each other.Q: What metrics does the VS Debugger Team measure related to the MSDN forums?A: The primary metric we've been using to date has been the percentage of posts answered in 7 days or less, with a goal of 80%. This doesn't mean that all posts will be answered in 7 days. Some posts require back-and-forth discussion with the customer to isolate the issue, or require lengthy investigation.Q: Who marks threads as answered?A: In general, we prefer it when the original poster marks the answer to their question, since only they know if their question has been completely answered. However, the forum moderators also recognize that, once someone has their question answered, doing bookkeeping on the forums is not likely to be a priority. Moderators will typically mark a post as answered if it appears that the original question was answered. This will happen as Moderators review threads. Usually this will happen after a few days have passed. This only happens in cases where there appears to be an answer. If a moderator marks a post as answered and you still have open issues, you can click Unmark as Answer so the thread will show up as unanswered.Q: Why are some unanswered posts deleted?A: In cases where additional information is needed to resolve an issue and the original poster of the thread has not responded after several reminders, one week after the last reminder, the thread will be deleted, so we can keep the forums focused on questions that have answers. This allows other forum participants to search and find issues that have been resolved, without having to wade through incomplete threads that do not contain any information that can help them resolve their issue. If the thread contained useful information (for example, if some data had been collected, but the problem had not yet been resolved), the thread might instead be changed from a question to a comment, so the information is not lost. This allows the folks looking for questions to answer to focus on open, active issues that can be resolved.Q: Why doesn't someone from the VS Debugger Team answer all new questions immediately?A: There are a few reasons. Primarily, we want to see an active user community develop where users help each other resolve issues and share tips and best practices. Additionally, the forums are one of many support mechanisms for Visual Studio as a whole. The forums are not intended to replace the traditional customer support methods, but rather to augment them. Most of the folks that respond to your questions are full-time developers, program-managers, or quality-assurance, rather than customer support.Q: Why did my post get moved?A: In some cases, a question gets posted in a forum that doesn't have the right people to answer that question. By moving the thread to a forum that is monitored by people more likely to know the answer, we can help you resolve your issue more quickly. When a post is moved, the moderator should add a response to the thread, indicating that the post was moved, and why. This can also help you find other community members with similar issues and experiences.If you have additional questions or concerns, please let us know.
Wednesday, November 28, 2007 9:18 PM
I have a tough time finding the correct forum/thread to use. I am trying to use Visual Studio 2003, VB. This means I could look under .Net Framework 1.1, Visual Studio, ASP.net, VB.net, and debugger (I think).
Searching finds related -but substantially different issues so the answers don't help. Where do you suggest I start looking to cut down the 4000+ posts that my searches are returning?
Thanks for any help you can provide,
Monday, June 15, 2009 8:36 PMModeratorHi Theresa,
Is there a specific question that you have? The answer as to where to look completely depends on what you need to ask. For example if you have a question about the VB programming language, then you would ask that on the VB forum, if you have a question about the Debugger tools in Visual Studio you would ask that here on the Debugger forum.
Andrew Hall. Visual Studio Debugger.
Saturday, October 02, 2010 12:04 AMthank you for you help
Tuesday, June 21, 2011 11:14 AM
How on God's good earth can a bug so grave be let to live in Visual Studio? Here are the details http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/a4a0d78d-f673-4532-9c52-1fe3f31b6fd2
Someone please make it top priority to answer, it is just embarassing and even more embarassing to keep people wasting time crying over it. This is just harassment for using your products.
Thursday, September 06, 2012 7:22 PM
>>posts answered in 7 days or less, with a goal of 80%
How does this correlate with the promise to MSDN Subscribers that:
"A Microsoft engineer will respond within 2 business days to your posting if the community hasn't already gotten you the answer"
It seems that the MSDN Subscription promise is at odds with your forum's policy.
Which one wins?