I was chatting with some of the people on our performance team (i.e. the people who are supposed to make sure VB is as speedy as possible), and they were talking about some plans they were considering to help gather public feedback on problem areas in the product. “What about the MSDN Product Feedback Center?” I asked. “We hadn’t thought of that,” they replied, “perhaps you should blog about it!” So consider it done. I am now officially encouraging everyone to report any major performance problems you’re having with VB using the MSDN Product Feedback Center.
To ensure that your bug gets the amount of attention due it, here are several suggestions:
- Put the word “Performance:” in the title of the bug.
- Include the general hardware specifications (CPU speed, memory, etc.) that you’re testing on.
- Include any changes to the environment that you’ve made (i.e. what tool windows are showing, which profile you are using, etc.).
And, most importantly:
- Include specific steps that will allow us to easily reproduce the problem.
The last point is important to ensure that we actually can do something in regards to your bug report. Saying “the product is slow,” isn’t going to help us. Saying “when I show the Autos window and then hit the Step Through toolbar button on this code, it takes several seconds.” is more like it. Remember, the more specific you are, the higher chance we’ll be able to fix the problem.
I’m also talking to Robert Green to see if we can’t get a specific “Performance” Problem Type added to the Feedback Center to help categorization. The wheels grind slowly, though, so it may be a while on that one.