No auto update should be included in Visual Studio. This is a sure way to break any legacy development environment.
The developer should have to initiate any updates to Visual Stuido, its add-ons or libraries used.
Our build server has multiple versions of Visual Studio on it and updating it will require a full retesting (many man months) of each of our solutions.
An auto-update / forced update 1 week before release of a major product would delay that products release months.
Add templated/generics for properties would do the same and be more useful.
Nice to have but will clutter VS, make VS install footprint larger.
Fix nuget/vcpkg to run on non-Windows platforms.
No. A nice to have. Less important than allowing wildcard file included in csproj files.
No. Ship a Windows 10 VM with VB6 development tools installed. Commit to maintaining that as a MS supported VB6 development environment until VB6 is retired.
Structure Visualization is a tiny fraction of all of the actions taken daily in Visual Studio.
Fix things that cost developer time each day, such as hand merging csproj files since they do not allow for wildcards in file names.
Focus on what costs developers time with the existing set of primary Visual Studio features and put the out of the ordinary use features into a second tier.
A strategic move; porting Visual Studio for Apple OS version to Windows; would allow a fresh start for VS without the 15 year legacy tools/features footprint.
A slim feature set tool like VS Code proves that it would work.
Publish via a blog the usage metrics for languages, tools, components of Visual Studio to show what is actually used so that a feature used by < 2% of users cannot drive Visual Studio's development plan.
Detect which methods / properties can be nested within another method (C# 7 new feature).
Short 10 line methods with a single purpose works well for small systems but fails to scale when there are millions of lines of code -> Spaghetti Classes