96 votes9 comments · Azure DevOps (formerly Visual Studio Team Services) » CI (Build) · Flag idea as inappropriate… · Admin →
I’m Will Buik, a Technical Product Manager on Visual Studio’s IDE team and I am back with an update. We have added an experimental feature to Visual Studio “15” Preview 5 that improves the time it takes to load Solutions. The feature is disabled by default, but you can turn it on through Tools→Options, “Projects and Solutions”→General→“Lightweight Solution load.”
We would love to hear your feedback about how lightweight Solution load works for you. If you are interested in participating in a quick user study to give us some feedback about the feature please fill out this brief survey: https://aka.ms/w2kt3j. We will reach out to you soon.
If you are interested in learning more about lightweight Solution load, check out the VS Blog: https://blogs.msdn.microsoft.com/visualstudio/2016/10/11/shorter-solution-load-time-in-visual-studio-15/
You can download Visual Studio “15” Preview 5 here – https://www.visualstudio.com/visual-studio-pre-release-downloads/
Thanks everyone, we look forward to your feedback.
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
Thank you for using Visual Studio and for your commitment to improving it. We are currently evaluating whether we will be able to include this into the product.
1,317 votesGreg Duncan commented
Allow us to pick a pattern of choice, and then have the IDE help us fall into the pit of success by supporting that pattern. So something like replacing the current code behind model with a plug-in'able/replaceable model, with MVVM being just one such model. If "code behind" is bad, then let the IDE help us by implementing a given pattern and not force use to jump through hoops to implement them. WPF/Silverlight/xaml's awesome databinding is the first step, now let's improve that by making the IDE "understand" a pattern of choice, like MVVM