Reopening this item.
Visual Studio Team
143 votesDave commented
The problem is that call stacks tell you where you're going next, not where you've been. It just-so-happens that in a synchronous world it tells you both. In Rx queries specifically, what we really need is a "query stack" that tells us where we've been, relative to where we currently are. I think that would make debugging async queries much easier. And of course, the same view could be used to simplify debugging Ix queries as well.
1,976 votesDave commented
For me, this applies to having multiple C# projects in the same solution. It's especially slow when each project targets a different platform; e.g., Client Profile, Silverlight 4 and Windows Phone 7.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to include this into the product.
Hello again voters and reporters for this UserVoice item
Visual Studio 2017 RTW, released yesterday, contains fixes to many of the worst issues we are aware of that caused typing delays. To get the benefit, if you haven’t already done so, please download it today from https://www.visualstudio.com/downloads/
We’ve also included enhanced typing telemetry in the new release, so we can continue to focus on improving those issues that remain, and we’ll alert you via the Visual Studio Performance Center (see https://blogs.msdn.microsoft.com/visualstudio/2016/10/10/faster-visual-studio-15-startup/ for details) when an extension is slowing your typing down.
We’re not done: we intend to make further improvements to typing responsiveness in updates to Visual Studio 2017.
Mark Wilson-Thomas and Hemchander Sannidhanam
Program Manager and Engineering Manager
Visual Studio Editor Team