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...
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...
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.
For God sake STOP odd VS versions number, restart with 2020 this year, please.
it seem need to change the name of visual studio to visual garage not VS version
I’m no one, but I wonder why are the odd numbers bothering you ?
Your code wouldn’t handle a future “2021” version of VS ? or would “2022” be a better release year ?
+1 … digging seeing “2019” every time I open your product in 2020.
I was assuming that since there’s going to be the major new .NET 5 release, that Visual Studio would bump up to VS2020 as well. But looking at the roadmap, it doesn’t actually say what the plans are for this.
There’s previously been discussions about dropping the whole year naming, and moving to an evergreen model like Chrome where it’s constantly updated, and the version number largely becomes irrelevant.
It's mostly a "little bit here and a little bit there". Nothing that makes be being excited or outstanding or something I would say "hell yes!". And half of the roadmap is very vague. Like
- "Improve the XAML Designer for .NET Core WPF and for UWP".... improve, how? What are the improvements? Is there anything specifically planned or do you just "See what people say and work on fixing a bug or two"?
- "Debugging...
I'm glad there's not a lot of big things this time. There are a huge amount of bugs that need to be fixed, and I'm hoping this means the leadership will get serious about fixing them. As a programmer for 20 years, every team I've ever worked on, would be very cautious about adding new features if there were a lot of bugs to fix. Adding a lot of new things while you are in...
God yes. Please make VS a 64-bit process. You can see improvements being made in this area, such as moving stuff to out of process. But please, please, please keep going in this area. It’s a daily pain point.
And again no word about 64 bit vs in replays 🙂
Thanks for the feedback Max. Regarding Git and GitHub, we are working on a new experience that will replace Team Explorer and take care of the navigation issues we currently have. This new Git experience will be coming as a preview feature very soon!
Max,
Hi, I am the PM for XAML tools for desktop apps and wanted to give a bit more context as you're right we're a bit vague in the roadmap as there is a lot of potential working going on in those two areas but we've not locked 100% on all the plans.
Some areas where we are investigating right now:
1. For XAML Designer, we're working on Suggested Actions which is still in development that will make...
To be more productive with Visual Studio, please restore the old new project dialog and the old start page, one of the most voted and most commented suggestion and one of the most ignored by Microsoft.
Knowing what is Microsoft doing this past years i’m more interested on what good and productive features Microsoft broke or remove in future versions of Visual Studio than new non-demanded features.
Have you tried Start Page+(https://marketplace.visualstudio.com/items?itemName=YannDuran.StartPagePlus)?
Nice to see some efforts towards fixing “async” problems. Are you also going to add “async” to the dictionary and make it more official-sounding?
(That was a joke, “async” isn’t actually a word.)
https://developercommunity.visualstudio.com/idea/583945/improve-asynchronous-programming-model.html
👆 Currently the fourth-rated suggestion in .NET feature requests. Thank you to all who are also feeling the pain and have voted as such!
I would like to see more attention on .NET Core Windows Desktop development. Our company heavily relies on Windows Forms and we would like to migrate do .NET Core, but the designer is not available yet.
Yes, that's a very good point and we will include information about WinForms in future. We have a blog post coming up in the middle of March with an update on WinForms Core designer. The work on it is in progress, we keep adding support for more features and controls and, as you mentioned, by the .NET 5 time frame we plan to get a mature version of the WinForms Core designer. You can check...
I’d also like to see WinForms plans mentioned in the roadmap. My understanding is that the WinForms team are aiming for the designer to have feature parity with .NET Framework capabilities in the .NET 5 time frame. Surely that’s noteworthy?
Still no sign of the non-modal start window hinted at by Pratik Nadagouda [MSFT] last July.
https://developercommunity.visualstudio.com/comments/642174/view.html
103 up-votes, and it’s still not “top customer feedback”. 😒
Just use my Start Page+extension. They’re never going to give us what we ask for because it doesn’t fit with what they want. Either that or they just don’t want to admit the whole Start Window was a mistake from the beginning.