The official source of product insight from the Visual Studio Engineering Team
On October 17th 2013, we announced the General Availability (GA) of Visual Studio 2013. We would like to thank everyone who took the time to share their thoughts while testing the pre-releases of Visual Studio 2013. While we read and consider all feedback from our community (Connect, UserVoice and Send-a-Smile), as with most development projects we could only implement some of the features and suggestions.
Since the GA, customers have adopted the product at a rate that is higher than that of Visual Studio 2012! Now that you have had about one month to use the product, we’d like to hear what you think about it. Let us know your impressions by taking the Visual Studio 2013 RTM survey.
We do these surveys with most of our public releases, and they help us gain deep insights on how we are doing with core areas such as quality, reliability, performance and overall satisfaction.
In this survey, we’re also looking for your opinions on areas such as .NET compatibility, project/solution compatibility and project type usage. Your input will help us continue to improve Visual Studio as we start planning for our next version. We greatly appreciate your feedback.
Deon Herbert Program Manager – Visual Studio Team
@Ben - Can you, please vote on the related User Voice items we have:
We use that to prioritize feature requests – based on the level of interest from the entire Visual Studio user community.
Keep the feedback coming!
@Jan - can you, please create an item on visualstudio.uservoice.com? This will let others vote on it, allowing us to see the community's interest in this!
I like all the new features -- they have been a real timesaver for me at times. And while it works great on a developer uber-box, I've seen it unusable on a lesser machine.
Many of my favorite addins won't install on 2013 without some manifest hacking because the developers haven't been able to update them for the new version. Since rapid spins are now the new norm, it would be nice if it were fixed so this won't be necessary.
@Kerem, For Preview and RC, we released all SKUs (Including Pro and Ultimate). In most cases users get the full fledged Ultimate SKU to try out the breadth of new things in Visual Studio. CodeLens was and still is an Ultimate feature since Preview/RC, and Peek on Pro+ SKUs. If something isn't showing up and it should be, do file a bug, and we'll look into it
What Robert said:
"Bring back the setup and deployment project, you really are not listening to your developers stop lying that you are.
Bring back the old setup and deployment projects!
Adding my voice to the chorus: bring back the setup and deployment project. Outsourcing this vital element of internal software releases is not an acceptable choice. Whatever incorrect reasoning that was applied to this decision needs to be identified and understood, then purged so as to not be repeated. From the outside this appears to be a giveaway at my expense to the stakeholders of a company that clearly does not have the ability to provide a simple packager. Whatever promises that were made between them and Microsoft cannot possibly have been met given the lack of the most basic utility and the widespread dissatisfaction with what we have now.
No migrateable Setup - very, very, VERY bad. Have to stay with VS 2010
In Visual Studio 2013 have missed the feature of package & deployment, very sad. It has introduced very most passinating feature to support reponsive design to work on differernt devices (iPhone, iPad, smartphone phone) etc.
I am suggesting a article listing all features of Visual Studio 2013 www.technologycrowds.com/.../visual-studio-2013.html
VS 2013 has some really nice new features, but taking away the setup and deployment project is simply unconscionable. A powerful tool like Visual Studio should have it's own installer. Aside from the problem created for new projects, upgrading an existing project goes from a simple task to becoming another PROJECT. What ever happened to servicing customers? If we developers treated our customers like Microsoft treats us, we would be out of business.
Please, remove InstallShield LE Project from VS 2013.
It's a shame and it makes me crazy!
Thank you all for completing this survey. The response was truly amazing!
The team will now analyze each of the responses to the survey. Your feedback will then help guide our features and priorities for the next version of Visual Studio.
Thanks for taking the time to share your opinions and experiences.
Visual Studio Program Management Team
"We just completed our recommendation for VS 2013 and decided to stay with VS 2010"
SAME HERE we have hundreds of installations. This is CRIMINAL and you should be SUED
"We use [user voice] to prioritize feature requests – based on the level of interest from the entire Visual Studio user community."
You're joking, right??
If you really are using it, then you've got the column sorting the wrong way!