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
Bring back the setup and deployment project, you really are not listening to your developers stop lying that you are.
We just completed our recommendation for VS 2013 and decided to stay with VS 2010 for as long as possible due to the missing setup and deployment project.
All comparisons to VS2012: I like the project/solution compatibility and the new "peek". The UI is a little better and TFS integration is a little better. One annoyance is that the Intellisense doesn't refresh if I have multiple projects open (in different instances of VS2013). Lets say I have an MVC project in one window and a class lib open in another (the MVC project references the class lib). If I make changes to the class lib, I have to restart my VS2013 session for my MVC project or Intellisense doesn't pick up the changes. It compiles fine, but the editor reports errors (squiggly red lines) and changes to properties/methods/interfaces, etc. don't appear.
I like the new Dark theme in VS because it relieves my eyes, it would be great to do the same in Office and all Windows. You should take that into account, many of us, programmers, spend 12 hours a day or more in front of a monitor (or two), in few years I will not see very clear.
I agree with the other guys, bring back setup and deployment project, but, do we really need it? Now you download projects from Windows Store, right?
I meant, applications, not projects from Windows Store.
For the most part I'm happy with VS2013. An area for improvement I would ask for is an improved debugging experience with Lambdas and LINQ in general. Also, keep up the language evolution. I love new language features!
I love the fact that on the toolbar you can choose what web browser to run your web app from. Also, I love the new color scheme. I am new to wpf but I am getting the same error in 2013 that I was getting in 2010 when I run the application and that is "application cannot run in the same process...".
InstallShield LE is extremely LIMITED, can't run custom action, won't allow SQL scripts, can't set up a project for Updating. Its just a major nightmare. At this pace I will start looking away from MS Visual Studio. I mean its like selling a great sports car with a very poor engine!!. What a disappointment.
I love VS2013. I like the default look and feel of it (more like 2010), I LOVE being able to edit and continue in 64 bit code (sold me immediately), and it has other handy features like seeing all references to methods and properties (which I guess is now disabled by default).
Really liking all the changes. I'd love to see improved debugging experience with Lambdas and LINQ like Ben suggested.
A roadmap of upcomming 1 to 2 year changes to Visual Studio and .NET would be great.
This would help our plan for the ~50% our apps which do not fit the app store and do not fit cloud based version control.
For most of our projects we will be staying with 2010 because of the loss of the setup and deployment project. InstallShield LE is terrible.
Visual studio needs better rapid dev mode to allow non coder to bring app idea to life
I like VS 2013, I can do what I want to do better than before. My development work is mostly C++ native, little UI, very basic in a sense. Minor problem: I miss the ability, when debugging STL, to set a watch on a vector element by means of array index. I can inspect vector elements in other ways (autos, hovering), but miss the opportunity to keep a watch.
Fix a windows deployment to. Don't care if it's the old setup and deployment, something by flexarea, or something else, but what we have to work with now is such rubbish I wish I had never upgraded
I use WiX for my installers and it suits me just fine because I'm not afraid of editing XML files.