I am with @HrumHrum , I need to decide whether to upgrade my team's legacy 2015 VS solutions to work with 2019 or wait for the next VS release. It would be nice to have a ball park date for the next release of Visual Studio. As a side note, it's sad to see what appears to be Microsoft's abandonment of their development support for .Net and Windows OS specific development tools in favor of VS Code/NodeJs/NPM open source stack. The one thing that Steve Ballmer got right was his "Developers, developers, developers..." address at the MS yearly company meeting a decade or more ago at Safeco field (I was an MS blue badge back then and I was there). If you want to promote your OS/Cloud offerings, expand and support your developer community, that was Ballmer's message and that strategy worked. While I'm on a roll here, deprecating the Visual Studio Load Test Framework was a huge mistake IMO (I still use the Load Test framework - world class perf/load/scale test tool and you can drive it with C# which is a language far superior to NodeJs IMO but don't get me started just look at how many data type possibilities there that result in a dynamic type conversion in JavaScript and the introduction of the +++ operator, geez what a joke, anyhow I digress.). The team that supported the Load Testing Framework may not have proven that their work pays for the cost of their development but the problem is that Microsoft does not appear to be measuring the indirect revenues related to developers who choose, evangelize and support Microsoft products.

I am with @HrumHrum , I need to decide whether to upgrade my team's legacy 2015 VS solutions to work with 2019 or wait for the next VS release. It would be nice to have a ball park date for the next release of Visual Studio. As a side note, it's sad to see what appears to be Microsoft's abandonment of their development support for .Net and Windows OS specific development tools in favor of VS Code/NodeJs/NPM open source stack. The one thing that Steve Ballmer got right was his "Developers, developers, developers..." address at the MS yearly company meeting a decade or more ago at Safeco field (I was an MS blue badge back then and I was there). If you want to promote your OS/Cloud offerings, expand and support your developer community, that was Ballmer's message and that strategy worked. While I'm on a roll here, deprecating the Visual Studio Load Test Framework was a huge mistake IMO (I still use the Load Test framework - world class perf/load/scale test tool and you can drive it with C# which is a language far superior to NodeJs IMO but don't get me started just look at how many data type possibilities there that result in a dynamic type conversion in JavaScript and the introduction of the +++ operator, geez what a joke, anyhow I digress.). The team that supported the Load Testing Framework may not have proven that their work pays for the cost of their development but the problem is that Microsoft does not appear to be measuring the indirect revenues related to developers who choose, evangelize and support Microsoft products.