Tell us about VS2010 Beta2


Last week we shipped Beta 2 for broad distribution.  Many of you have already sent us comments and improvement suggestions (thanks!)


At this point we are down to our final set of bug fixing, perf tuning, etc.  We’re very interested in your feedback so we can take action on it before we ship the final version.  To help make it easy, you can take this simple survey.


image


One thing in particular we are hearing a lot of feedback on is performance.  We are working hard on the next round of perf improvements.  You can supply your feedback through the survey.  When you give us your feedback, the more actionable you can make it the better.  We need to know what operations you are doing (like editing, debugging, etc), what kind of hardware you have (CPU, RAM, disk), and your hosting scenario (main machine, running in VM, terminal server, etc).


Thanks in advance for your feedback!


Dave


P.S. If you’d like to talk to me directly about your performance experience, you can reply here or e-mail us at DevPerf@Microsoft.com.


 

Comments (2)

  1. Makingsense says:

    What the heck do you mean by "actionable" ?

    P.S. Your microspeak terms don’t make sense outside of the empire’s walls.

  2. David Berg says:

    Actionable isn’t Microsoft speak, you can find it in the dictionary (e.g. http://dictionary.reference.com/browse/actionable).  In this case, we’re refering to definition 3 "ready to go or be put into action."

    What we mean by that is that it helps if the problem is phrasaed in a way that is easy to take action on.  For example, if you tell us that "Visual Studio 2010 is slow" that’s not actionable if we don’t observe the same behavior.  However, if you say "When I open a 5,000 C# project solution on my <machine specs> it takes 2 minutes before VS becomes responsive." then that’s something we can go off and replicate and see if we have the same experience.