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
After over 15 years of Microsoft development I feel that the end is nigh. The removal of the old Setup and Deployment projects and their replacement with InstallShield LE is the final straw.
Also sticking to VS 2010. Why would anyone switch when it already has a streamlined, effective interface and all the setup and deployment you need? I don't know what you were thinking, but it clearly involved putting customers on mute.
Bring up the setup and deployment project.
To be honest, Visual Studio is the only reason I stay on Windows. I can't continue to use an IDE that is no longer updated (VS2010).
VS2012+13 are a disaster - I've tried them each for several weeks, they're less usable, and I don't like the direction MS are going, and their ignorance to customers.
It's a shame, I used to like developing under Windows.
"Your feedback will then help guide our features and priorities for the next version of Visual Studio"
We've heard that one before.
We just started to migrate from VS2010 to VS2013 and have like many other here discovered that Setup is missing. The Installshield LE is UNUSABLE. I rarely complain about MS, am a big fan of MS and live with issues that we all face daily, but this dear VS Studio Team is inacceptable. Don't take away tools that are working fine without providing something decent instead.
InstallShield the way you deliver, is no good. The only way to make setup work is by buying the 2000 EUR Version.
Please Microsoft, remain professional and do you what you always did, give developpers tools, otherwise you will end up like many others who did not listen to their customers. You lost already the Phone Battle, do you want to loose the Developper battle as well.
Customers don't forget.
Stupid question but a running instance of VS 2013 does NOT appear in windows 8.1 taskbar!
Bring back the setup and deployment project
Visual Studio developers need to learn you to create their own setup and deployment projects. InstallShield Castrati is just a teaser to get you to buy an expensive project. WiX gives you a decent Visual Studio plugin, Votive, for native Windows installers. I am glad I am not on one of the teams held back to VS 2010 just because the lead devs did not want to learn how to deploy their own software.
it crashes more than ive ever seen in my life. I am finding it impossible to port my solution from VS 2010 to 2013. I will be recommending NOT upgrading to visual studio 2013 for the near future.
I've been running VS2013 on the following setup:
CPU: Intel(R) Xeon(R) CPU X5450 @ 3.00GHz 2.99 GHz
OS: Win7 64bit
I've installed updates as they became available (update 2 took 2 hours on a speedy corporate network!), but have suffered constantly from hangs, where the interface became unresponsive for minutes. I disabled Mindscape Web Workbench and Web Essentials 2013 plug-ins, thinking these might be the cause, but the problem rears it's head periodically.