The existing vertical document tab extension is uninstallable by default because it doesn't play nicely with increased async behavior in VS2019. There's a way to hack the installer to force it into 2019; but rather than letting telemetry show I did that I'm letting whatever non-opt outable telemetry VS/W10 have to show that I'm actively avoiding 2019 despite having it installed in favor of 2017.
MS has said that they can't fix the extension, and that the right solution is to bring the feature into the main VS code base; with no indication of progress other than saying it's under review, and a 3rd party survey asking what we think is needed most for tab managment.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
New version awareness tends to come when you first try to find something and it's a case of "Grrrr! Where on earth have they hidden SSIS this time?" or something to that effect. I pay little attention to icons.
I'm on 2017 by the way (had to check). That seems to be okay.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
I decided to do a speed test the other day recording project startup times and also build times for a small web application. I'm getting pushed to migrate around a dozen small to medium sized web applications from .NET 4.0 to .NET 4.6 to take advantage of a new (fairly expensive) suite of widgets we bought last year. I've been dragging my feet as it means leaving my beloved VS 2010 which I've become quite fond of over the decade. Why would this matter?
Sure, I've tried the newer versions, VS 2015, 2017, and now 2019. None can match the startup and build times of VS 2010.
Startup time in secs: (double-click to usable)
a: 2010 - 6.5
b: 2017 - 24.0
c: 2019 - 15.0
Build time in secs: (F5 after making a change)
a: 2010 - 9.5
b: 2017 - 23.0
c: 2019 - 16.5
It's getting better, but a difference of 6-7 seconds every time I need to debug is tangible. I suppose there is a price for progress.
Another thing that annoys me is how much bloat/cruft comes with using third-party components....add one widget to the project and it adds 3 dozen dlls along with the language packs for de, es, ja, and ru.