can't set indent level to 4 spaces in vs 2017

Reported by david m chinn Apr 13, 2017 at 11:20 PM windows 10.0 Visual Studio 2017 version 15.1 fixed in: visual studio 2017 version 15.8 preview 5 Fixed In: Visual Studio 2017 version 15.8

i have much code written previously in 2015. all of it is tabbed to 4 spaces.

with the new ide i have tried to set 'tools\options\Text Editor\All languages' to tab and indent size to 4, and set 'insert spaces' radio button.

however, the autoindent insists on using 2 spaces for each tab.

This shows up whenever i hit a carriage return, and also when formatting an entire file by deleting and re entering the last '}'

please help...!

Add comment Show 12

david m chinn · Apr 14, 2017 at 06:15 PM 0

i stumbled onto another clue.

formatting always formats to two spaces in my environment, for any file **included* in the project. No matter what values i enter into .... Tools -> options -> editor -> All Languages -> Tabs

If i exclude a c# file from the project, and then reformat (by removing/readding the last '}'), the autoindent is applied correctly, as specified in Tools -> options -> editor -> All Languages -> Tabs

Likewise, if i create a new c# file, it starts out with 2 spaces indent, and ignores the tabs setting as long as it is included in the project. But when the file is excluded from the project, and then re opened, it can be reformatted correctly.

as a lark, i checked the tab spacing under every language... basic, c#, c++... etc, etc, etc; everything set to 4.

it seems like something in the environment is over riding the tab settings?

thanks for your continued attention.

Visual Studio Feedback Systems ♦♦ · Apr 14, 2017 at 08:45 PM 0

Thank you for your feedback! For us to investigate this further, could you please tell us if the Tool-> Options setting turns back to 2 or if it stays at 4? We're trying to understand if the setting is reverting or if it's being ignored. We look forward to hearing from you!

Jordan Marr · Apr 19, 2017 at 10:05 PM 1

I am now having the same problem (VS2017 Professional). But it is only happening in my ASP.NET Core Web project. I also have a domain class project that is unaffected.

david m chinn · Apr 20, 2017 at 04:43 PM 0

the entered settings do not change.

another datapoint: if the file is included in the project, i can set indents to an arbitrary value (6, 8, 12, etc), and the environment continues to indent at 2.

excluding the file from the project, and the autoindent will use the set value.

Hemchander Sannidhanam [MSFT] · May 08, 2017 at 09:29 PM 0

Thank you for your feedback! We have determined that this issue is not a bug given you are experiencing this issue due to an .editorconfig file in the code base. Since VS 2017, Visual Studio started respecting .editorconfig settings and that explains the behavior that you are seeing.

Simon Needham Hemchander Sannidhanam [MSFT] · May 09, 2017 at 01:29 PM 0

This is a bug in the Options dialog. You can't continue with the current behaviour of respecting a .editorconfig file but still allowing a user to configure/change tab settings in an Options box that will be ignored!

If tab settings in the Options dialog are ignored/superseded they need to show as disabled in the Options dialog.

For me this issue was extremely confusing issue as VS 2017 had found a .editorconfig file in a parent directory - higher up than my solution folder!

Hemchander Sannidhanam [MSFT] Simon Needham · May 09, 2017 at 07:48 PM 0

Simon,
We have thought about solving the problem that you have encountered. We will consider addressing that in a future release.

Thank you for your feedback!!

garynicholas Hemchander Sannidhanam [MSFT] · Feb 10 at 10:13 PM 0

In general I find it very frustrating/annoying that you guys always try to dismiss/downplay legitimate issues like this one - "...this issue is not a bug" really? It most certainly is as Simon pointed out - how stupid do you think everyone is? What do you accomplish by denying the obvious issue - only pissing off your end users.

Hemchander Sannidhanam [MSFT] · Feb 13 at 05:00 AM 0

We appreciate you taking the time to report this problem. We are currently prioritizing problems that are impacting a broad set of our customers, so we may not be able to investigate this one immediately. We know this problem is important to you, so we will continue to monitor it.

Blair Wang [MSFT] ♦ · Jun 08 at 02:14 AM 0

Thanks for reporting this problem. After careful evaluation of the problem impact & severity we are closing this problem as low priority. We understand that this might not be an ideal resolution for you, but be assured that we don’t make these decisions lightly. We prioritize problem investigations by impact and severity for a broad set of customers; the impact of this problem is limited relative to other existing problems.

We have made significant improvements to the product over the past few months, notably in the areas of performance, reliability & general quality of the product. It is possible that this problem has been addressed in the latest version of Visual Studio. We encourage you to update to latest version of Visual Studio and continue to give us feedback.

Blair Wang [MSFT] ♦ · Jul 13 at 03:33 AM 0

Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!

Blair Wang [MSFT] ♦ · Jul 27 at 01:24 AM 0

The fix for this is now in our latest Visual Studio Preview release. If you'd like to try out the fix, you can access the preview build here: https://visualstudio.microsoft.com/vs/preview/

Best Solution

Added a solution by Simon Needham · Apr 25, 2017 at 07:46 AM

You may have an (auto-generated) .editorconfig file in your code solution that is over-ruling your Visual Studio settings.

This happened to me when I created a new Angular project with the Angular CLI. It created a .editorconfig file in the root of the project source code. I then added an ASP.NET Core Web Api project in a child folder. Even though you can't see the .editorconfig file in the parent folder when working on the WebApi project it was pulling in the config from that file and overriding my VS tab-is-4-spaces setting.

I got the clue from this issue (https://developercommunity.visualstudio.com/content/problem/44816/tab-inserts-2-spaces-instead-of-4.html)

For me I fixed the issue by adding a specific *.cs setting with an ident_size of 4. My JS/TypeScript/HTML Code in VS Code remains the same and sanity is restored within my C# Web API project.

[*.cs]
indent_style = space 
indent_size = 4

Add comment Show 5 · Share

david m chinn · Apr 25, 2017 at 03:06 PM 0

thanks so much!

one comment: i did a search through the entire solution, but could not find a .editorconfig file anywhere.

but i added the file (with simon needham's content) in the same folder as the .sln file and things were fixed.

Thanks again!

Jordan Marr david m chinn · Apr 25, 2017 at 08:27 PM 0

That was indeed the problem! Thank you.

Simon Needham david m chinn · Apr 26, 2017 at 07:05 AM 0

Hey cool, glad it helped.

NB that rogue .editorconfig file could be in any of the parent directories of your solution or... you've found another way that Visual Studio tab settings can be secretly over-ruled.

I definitely think the VS config dialog box could do better. If the tab settings are being over-ruled then they should be disabled in the dialog box along with a message explaining why (and displaying the path to the over-ruling config file would be perfect!).

Joshua Morton · Sep 26, 2017 at 09:26 PM 0

I found a .editorconfig file in the root of my c drive (c:.editorconfig). When I deleted this file, this issue went away for me.

Ben DeHaan Joshua Morton · May 15 at 07:17 PM 0

THIS SOLVED IT FOR ME

Added a solution by Blair Wang [MSFT] · Aug 17 at 09:32 AM

This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://visualstudio.microsoft.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.

Add comment · Share

Added a solution by david m chinn · Apr 15, 2017 at 03:33 PM

the entered settings do not change.

another datapoint: if the file is included in the project, i can set indents to an arbitrary value (6, 8, 12, etc), and the environment continues to indent at 2.

excluding the file from the project, and the autoindent will use the set value.

Add comment Show 2 · Share

david m chinn · Apr 19, 2017 at 06:38 PM 0

any further clues? or, is anything more information required?

can y'all at least repro the problem?

in fact, i've uninstalled and reinstalled vs 2017 and the problem persists.

david m chinn · May 08, 2017 at 01:53 AM 0

to be clear... this problem has been resolved by the note from simon needham

Developer Community

Get help from our community supported forum

can't set indent level to 4 spaces in vs 2017

Solutions

Try Microsoft Edge

Developer Community

Get help from our community supported forum

can't set indent level to 4 spaces in vs 2017

Solutions

Related Problems