Top 10 customer issues in Visual Studio 2005


MSDN Product Feedback Center is one of the best things we have done recently in an effort to stay better connected with our customers.  Having this as a feedback mechanism to help understand what is foremost on our customers’ minds in Visual Studio 2005 has been super valuable.  The “voting” feature in MSDN Product Feedback Center has helped us focus and prioritize working on issues that have the most customer mindshare.  I recently looked at the top vote-getting customer issues, with a customer average rating higher than 4.0 to understand how well we are responding.  Here is a list of the top customer issues and a brief commentary on how we have responded to these: 


Title: Deploy updated/new icon sets with Visual Studio


Average Customer Rating: 4.79      


Votes: 813                  


Issue Type: Bug          


Description: Shipping new icon sets was originally postponed for the next version but was fixed for Whidbey due to the overwhelming feedback on this bug.



Title: Edit and continue support for Visual C#     


Average Customer Rating: 4.55      


Votes: 399                  


Issue Type: Suggestion                    


Description: Edit and continue was the most requested feature for C#. This is another feature we were working on for a future release that we fit into Whidbey based on customer requests. 


Title: Where did components area on Web Forms go??


Average Customer Rating: 4.71      


Votes: 178                  


Issue Type: Suggestion                    


Description: Twice we resolved this issue as “Won’t Fix” but because “kzu” kept pushing, reopening the bug and insisting we reconsider, we did and fixed it for Beta 2. I want to thank kzu for driving this issue for the community. 


Title: Tray Icon support is limited: System.Windows.Forms.NotifyIcon doesn’t support Balloon Help without P/Invoke


Average Customer Rating: 4.54      


Votes: 174                  


Issue Type: Bug          


Description: To Kevin Daly’s point in the discussion – we do want to make “Windows Forms the *best* way to do Windows UI”. I’m really glad we fixed this bug.



Title: Enable Direct Downloads          


Average Customer Rating: 4.78      


Votes: 76                    


Issue Type: Suggestion                    


Description: This is a good example of the range of issues we receive and respond to in the PFC. This is not a bug in the product but is key to the beta process. 


Title: ASP.NET Web Forms templates shouldn’t use HTML that is considered obsolete      


Average Customer Rating: 4.7        


Votes: 67                    


Issue Type: Suggestion                    


Description: Old templates were replaced by 2 sites designed to adhere to the standards and avoid obsolete HTML.



Title: MSFB Ctrl+f5 of a console app doesnt cause the cmd window to stay around with “Press any Key to continue” message                                  


Average Customer Rating: 4.77      


Votes: 53                    


Issue Type: Bug          


Description: An Everett feature we originally removed was added back in. 


Title: Intellisense completes word on space as well as tab       


Average Customer Rating: 4.46      


Votes: 50                    


Issue Type: Bug          


Description: Here we added customizability after overwhelming feedback was recieved



Title: Client Side Validation               


Average Customer Rating: 4.81      


Votes: 48                    


Issue Type: Bug          


Description: This bug was found internally as well but the customer found it 3 months earlier!  


Title: asp:Menu control only works in IE            


Average Customer Rating: 4.85      


Votes: 47                    


Issue Type: Bug          


Description: This bug has some amusing workarounds posted…


Namaste!


 


 


Comments (14)

  1. TAG says:

    Hey ? What about others (from total 42) issues in your search query ?

    http://lab.msdn.microsoft.com/productfeedback/SearchResults.aspx?text=&stype=1&fields=1&type=0&category=0&os=0&oslang=0&status=0&msstatus=0&resolution=0&chgdays=&validation=0&votes=47&voterating=4&workarounds=False&attachments=False&product=0&version=0&creator=&createdWithin=&submissionlang=0&productlang=0

    Comment on them or change your wording

    from "Here is a list of the top customer issues"

    to "Here is a list of the top customer issues I’m willing to show how good we react on them, all others regarless on number of votes and score are always ignored by us, and this my posting will not be exception from this rule"

  2. Somasegar says:

    I just changed the format of this blog entry since the table that I had before didn’t seem to work in certain situations.

    The content is all the same.

    – somasegar

  3. Somasegar says:

    The list that I posted was generated by taking all the issues we fixed with a 4.0 rating or higher and then ordering the list based on the number of votes. The intent was to show the customer impact on the product and what were some of the popular issues that we fixed in the product. Andriy is absolutely right that this is NOT the entire list of the top issues with a higher than 4.0 rating. This is focused on the list of the top issues that were fixed in the product. You’ll notice that some issues were originally resolved as “Won’t Fix” but then we changed our position because of strong customer response. I really love to see passionate Visual Studio users changing the direction of the product. This is how software development should work. It’s true that there are some great feature requests we couldn’t do in Whidbey but we’re definitely not ignoring that feedback. That information is extremely valuable and we will mine it for future versions. In fact, all “Postponed” bugs and suggestions will be rereviewed. We postponed many issues because we simply don’t have time to address them and maintain our current schedule goals. I think you’ll see many of those “Postponed” resolutions change to “Fixed” when we start working on the next version of VS.

    I really liked how Paul Krill calls this “The user-driven improvement list” in his article that you can read at http://www.infoworld.com/article/05/05/31/HNvschanges_1.html

    – somasegar

  4. Jason Haley says:

    Interesting Finds from today’s commute

  5. TAG says:

    Somasegar,

    Thanks for clarification.

    Do not understand me wrong – but there was no word "Fixed" in your posting on describing your Top10 selection.

  6. Somasegar says:

    Andriy – Thanks for catching this. Not at all an issue. I am glad I got an opportunity to clarify the intent and to encourage more customer feedback.

    – somasegar

  7. interscape says:

    Thanks for adding icons for us to use in Beta 2… now can you guys add PNg images and do a better job categorizing them? For example, paragraph alignment, bold/italic/underline, and text color icons should all be under "word processing". It might be helpful to dump them in app-specific folders too, like "Word" and "Excel".

    VS2005 rocks. Your team has done a great job.

  8. I blogged the other day about the top customer issues that we have fixed based on customer feedback via…

  9. munjingugi says:

    where are my VB C# VWD templates in my Visual Studio 2005 IDE?

  10. Methew G. says:

    I have no idea why people curse support people, they are not at all related with the development procedure. I am glad you pointed out these bugs and their remedies.