The Visual Studio roadmap has been updated to provide a peek into the work planned for Visual Studio through June 2020. It captures significant capabilities that we plan to add, but it’s not a comprehensive feature list. Our goal is to clarify what’s coming so you can plan for upgrades and provide feedback on which features would make Visual Studio a more productive development environment for you and your team.
Our roadmap is driven largely by what we learn through ongoing customer research, as well as the feedback we get via our Developer Community portal. These features and time frames represent our current plans but may change based on what we learn. If there are features that are particularly important to you, please be sure to vote and comment on the features in the Developer Community portal.
We often get feedback on the importance of an up-to-date roadmap for Visual Studio. We aim to publish updates more frequently going forward and we’re putting processes in place to make that happen. In that light, we’d highly appreciate if you would take a brief survey to let us know how to best handle the roadmap going forward.
Improving UWP Compilation times are not in the roadmap.
That is soooo saad. We've been complaining for years. The higher winOS you target, the worse it gets. It's close to unusable.
Here's just the latest thread: https://github.com/microsoft/microsoft-ui-xaml/issues/1517 https://github.com/microsoft/microsoft-ui-xaml/issues/1535
This won't go away with WinUI 3.0 - because that's UWP behind the scenes.
I do understand that it's not a top priority, but at least some things should be made faster for those with big RAM and/or fast HDDs - at this time, this does not seem to be the case. I have 64 GB of RAM doing nothing, and a 3 GB/s HDD,...
I’d love to see more work done for large solutions and the option to *disable* the AI-related features from the last several major releases. For those of us working on large solutions that regularly approach the 32-bit memory limit, I’d ***love*** to see devotion to perf improvements.
There are so many issues with Visual Studio 2019. Source control sluggishness, edit and continue not working, extremely high CPU usage—even when not compiling, frequent TFVC ‘not authorized’ errors, refactoring not working at times.
After months of waiting for fixes and butting heads with Microsoft support—nice people but way out of their depth—I have switched to Rider. Once they improve their Dev Ops integration, I plan to use that as my primary IDE.
Why are these issues not getting the team’s attention?
Why should I bother completing a survey, when most of the bugs VS I take the time to report get closed as “probably won’t fix”?
I think I might mark this survey “Probably won’t complete”.
Richard Moore wins the nerd internet this day.
Why does MSFT continue to ask developers to fill out surveys when it already has a feedback apparatus that allows for upvoting, commentary, and integration with existing internal development workflows with developercommunity? We’re already telling you what we want. You are telling us that you simply do not want to listen.