Spend more time fixing the little things.
Visual Studio has, no doubt, thousands of little bugs that, taken individually, do not make the bar for a given release. The accumulation of these little bugs over the years has significantly impacted the overall quality experience of using Visual Studio. Those little bugs are important - spend more time on them, rather than summarily closing them when they appear on connect.
David Kean commented
Thanks for the suggestion. Speaking for my team (BCL/CLR), we do spend a milestone or two every release focusing on what we call "customer love" features - which is exactly what you are suggesting. These are small features/bug fixes that are often requested and hit but aren't massive game changers. The best way to get these on our radar, is via user voice. For example, for Martin's issue below GetEnvironmentVariable - please file a user voice suggestion to improve this behavior so that when next scavenge the site looking for features - we'll see it.
I wholeheartedly agree with this. I would much rather have a rock solid and completely 100% trust worthy coding experience than to jump from one version to the next while little bugs keep piling up.
Enough already. I don't need a new UI, I don't need new language features. I need the existing stuff to work perfectly.
And please, don't give me that line that software is complicated and can't be bug free. That is the thinking of someone that could never land a 1 ton rover safely on a planet over 35 million miles away.
Work on the product, get it right, and stop screwing with the UI.
Martin Brown commented
I wish I could give this a thousand votes. I spend far too much of my day bashing my head against flaws in the .Net framework that are more kind of design flaws than code bugs and have been there for years. For instance today I'm trying to use GetEnvironmentVariable to get a path without the %environmentvariables% expanded. And I'm not the only one http://stackoverflow.com/q/7121846/20553.
Fixing existing problems is even more important than adding new features. But only as long as those fixes are released in a monthly schedule.
**** yeah good idea, MS are always obsessed with chasing the next big thing rather than just getting the basic VS working properly.
I think they need to slow down the feature creep (of VS, not necessarily the .Net languages), and speed up the release schedule so we get bug fixes sooner.
Time spent converting to WPF would've been better spent re-writing to get rid of bugs.