unable to remove indent guides

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

[regression] [worked-in:16.9.5]
Hi.
I just updated to Visual Studio 2019 v16.10.
I unchecked the two options under "Block Structure Guides" in C# options.
The indent guides are always visible.

Thanks.

---

Original Comments

Feedback Bot on 6/1/2021, 06:06 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Feedback Bot on 6/2/2021, 09:41 AM:

This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available, or the issue is resolved.

William Sade de Paiva on 6/22/2021, 04:05 AM:

Hi Joey.

Thanks for the fast reply.
Ok, It worked now.

“But”, before v16.10, it was not necessary to set this configuration.
Even in VS 2017, it was not necessary either.

It is not the first time Visual Studio 2019 changes its behaviour after an update.

Regards, William

trusomeg@gmail.com on 6/22/2021, 01:15 PM:

Workaround provided doesn’t solve the problem - options under “Block Structure Guides” in C# still doesn’t work. Also it’s misleading, because section with “settings that control whether code constructs such as if blocks are collapsible” is called Outlining, while we are talking about structure indent guides.

The issue is about setting called “Show structure guide lines” in Tools > Options > Text Editor > General. It ignores both options under “Block Structure Guides” in C#, making them irrelevant. So, you can either have both types of indent guides or none, which is a bug.

---

Original Solutions

Joey Robichaud [MSFT] solved on 6/21/2021, 00:04 PM, 0 votes:

Hi William,

The settings you disabled control whether code constructs such as if blocks are collapsible in your code. You will need to disable the “Show structure guide lines” in Tools > Options > Text Editor > General to disable the indent guides.

[JoeRobich]

This issue was resolved by #54079. It will be in Visual Studio 16.11 Preview 3.