You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd really like to have a way to opt-out of the new style. Folding XML comments is a way for me to get a rough overview of a class without having my view obstructed by the documentation I'm currently not interested in. I fold them in order to not see their contents and, judging from this point of view, would not consider the new behavior an improvement.
I suspect that there might be a setting to toggle this. I've searched the IDE for that option to choose which outlining style should be used and somehow revert it back to the one used in VS2013, but didn't find a way. Please let me know if I missed something and feel free to close the issue if this is the case.
The text was updated successfully, but these errors were encountered:
There isn't currently an option for this, but it's one we should consider introducing - I think this is the 3rd (and 4th) times I've heard this request.
Closing this issue as we've seen no reply to the request for more information. If you are able to get the requested information, please add it to the issue and we will retriage it.
Version Used: VS2013, VS2015, no Preview version.
Steps to Reproduce:
Expected Behavior:
Actual Behavior:
I'd really like to have a way to opt-out of the new style. Folding XML comments is a way for me to get a rough overview of a class without having my view obstructed by the documentation I'm currently not interested in. I fold them in order to not see their contents and, judging from this point of view, would not consider the new behavior an improvement.
I suspect that there might be a setting to toggle this. I've searched the IDE for that option to choose which outlining style should be used and somehow revert it back to the one used in VS2013, but didn't find a way. Please let me know if I missed something and feel free to close the issue if this is the case.
The text was updated successfully, but these errors were encountered: