I can further add to this... it seems every new version of Visual Studio consumes more vertical screen space.
Looking at old screenshots of the output window, for example, there was no title bar, no toolbar, and the horizontal scroll bar was adjacent to the tabs. In the space where today we can see five lines of output text, we used to be able to see 10.
The output window isn't the only culprit. Why does every window have both a title bar and a tab bar? Why does every tool window need its own toolbar?
Hi thanks for your votes and survey responses. We’ve closed down the survey now and are looking into options that would solve the underlying need that you’ve presented to us. However, due to prioritization of work, we will not be able to release this exact feature in a future update.
If you implement this, please make it configurable. I definitely do NOT want multiple rows of document tabs taking up even more vertical screen space.
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to address this suggestion in a future release. Thanks for capturing the pain points you feel when stepping through multithreaded applications while debugging. We will be providing an update soon.
Additionally, I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread. If you have other breakpoints in your application and another thread hits one, then you will be debugging in the mixed thread state as described in this item.
Program Manager, Visual Studio
"I wanted to clarify that the debugger will only ever complete a step on the thread from which the step was originated. So if you hit a breakpoint, disable it, and then begin stepping you should not stop on a different thread."
This is broken then. At least it was in VS2012 (the version I'm currently stuck using). If you're single stepping through code that is being executed in parallel across multiple threads, there's no guarantee which thread you'll end up in next.
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