Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
This post has been modified to reflect that the survey has closed, and instead updated with the results.
Thanks everybody for all the great feedback! We received hundreds of replies with detailed information and concrete examples for us to review. We have closed the survey and have started to process the data you provided.
The overwhelming majority of you have told us that Edit and Continue is important and you'd like us to make it even better. We listed scenarios where Edit and Continue is disallowed today and asked which ones impacted you the most. Here's what you said:
As you can see the most frequently reported problem is that Edit and Continue doesn't allow you to modify or add LINQ queries or lambda expressions.
The good news is we hope to address LINQ and lambdas (and more) in the next release of Visual Studio! In fact, we've investigated what it would take and the work is already underway to make the necessary changes across the Visual Studio debugger, .NET Runtime, and Managed Languages teams to make Edit and Continue play nice with LINQ queries and lambda expressions in vNext.
We'll share more about that and other exciting developments in future posts. Until then, a huge thanks from all of us on the Visual Studio team for helping us figure our what is important to you.