Improve the Structure Visualizer in Visual Studio 2017
In Visual Studio 2017, some parts of the Structure Visualizer from the Productivity Power Tools were added to Visual Studio.
Others were not included in the port.
This UserVoice item is intended to gauge broader feedback for the following capabilities which we've heard about from some users. If voting for this item, please feel free to give a priority on the following in your comments (as well as any other comments you may have):
1. Different in editor line colors per “block level” (i.e. colors indicate how deep you are only)
2. Different in editor line colors per semantic unit kind (loops are different from if branches are different from method body for instance)
3. Option to have solid lines instead of dotted
4. Structure depth visualization in the map mode scrollbar
Program Manager, Visual Studio IDE Team
Someone implemented the Structure depth visualization! :-)
#4 is the one I missed immediately. The rest probably is ranked #1, #2 and #3 to me.
Why I should have to spend my Sunday doing this is beyond me; but you're fucĸing welcome.
This covers #4.
#1, #2 & #3 Could be turned on in the source code and recompiled. But I'm not interested in those. If you are, you can find the code at: https://github.com/FS-NulL/VS-PPT
May I offer my sincerest fucĸ you to Microsoft for not bothering to do this. We've waited for about 400 days for this to never happen. For the past 400 days, I've been editing code in 2015 and compiling it in 2017.
And on a personal note to Mark WIlson-Thomas, for making us think Microsoft might have possibly considered re adding this, go sucĸ a dicĸ.
Hold on to your hats:
#4 is most important to me.
Our teams just recently switched from VS2015 to 2017 (Enterprise), and this is the most prominent missing feature.
@Mark any update on this? Its been over a year.
We have just updated to VS2017, and its disappointing to see PPT features deprecated in favour of a builtin implementation that has only 10% of the functionality.
The bare minimum that should be available (either in VS, or added on via PPT) should be what PPT 2015 offered, that is:
#4 (critical for productivity when working with 1k+ line CPP files)
#2 (colour by semantic unit is far more useful than by depth, depth is shown by tabstops!)
#3 (it was solid in PPT so why would you change it on a whim to dashes without leaving solid as an option?)
Michael Ketting commented
I just upgrades to VS2017 and was shocked that #4 is no missing from Productivity Power Tools. Getting strucutre Information in the map mode was essential to me when navigating source code.
Microsoft, you are a fucĸing disgrace.
#4 is essential for me! It helps tremendously to navigate in large source files.
all of them!
Yolanda B. commented
Please prioritize items #3, #1, #2, #4 for the Structure Visualizer in VS2017. I have grown accustomed to the colorized and solid structure guide lines that were once available in the Productivity Power Tools extensions pack.
Colin Mattson commented
1, 3 and 4 for C++ please! Was very disappointed about this when upgrading to 2017
As you have no problem not implementing this (We've been waiting all year). Why not open source the 2015 PPT extension, and let us do it for you?
#4 is very useful.
plz plz plz
Mark Wilson-Thomas commented
@Stephen: thanks for your comments. I wanted to let you know that although we don't have #1,#2 yet, you can customize the (default grey dotted) lines to a different color to help them stand out more, in Tools-Options-Fonts & Colors-Text Editor (Display Item is "Structure Guide Lines"). Pick an item background of your choice and press OK. Hope that helps a little.
@Peter, thanks for the input on increasing the number of supported languages - this is being actively considered.
Please prioritize #1 and #2. #3 and #4 would be nice-to-have, but don't "break" what was in 2015. I use a 2 space tabbing, and found that the dashed lines are very hard to distinguish and follow, which is what brought me here.
#2 and #3 !!!
and please for ALL supported language types in VS !!!
(aspx, aspx.cs, ascx, ascx.cs, cshtml, ...)
Another vote for #4 please. I've currently reverted to VS2015 in order to keep this functionality.