Visual Studio 2010 forces tab indenting

An anonymous reader writes: For years, Microsoft has allowed Visual Studio users to define arbitrary tab widths, often to the dismay of those viewing the resultant code in other editors. With the VS2010, it appears that they have taken the next step of forcing tab width to be the same as the indent size in code. Two space tabs anyone?

This is an issue how?

[Foredecker]

This tab thing makes Slashdot front page and the following didnt? Windows 7 way hotter than Vista off the line, now more popular than all OS X versions [engadget.com]. Okay then...

How is this tab things news or interesting at all? Here is what Brittany Behrens a PM for the editor team said:

Hi Brien,

Thank you for logging this issue. Before making this change we solicited feedback on the decision to combine Tab Size and Indent Size from a wide variety of sources, including public blog posts and forum threads, and found that the vast majority of user feedback was in favor of combining the two. If its seriously impacting your code to have Tab Size always equal Indent Size, it is possible to write a short editor extension to override the Tools->Options dialog and set the two options separately. If thats something youd be interested in, please let me know and Ill see about posting sample code for how to do this.

Im resolving this issue as By Design because we intentionally combined these options for VS 2010, but please feel free to post again here if you have any further questions or comments and well be happy to help.

Thanks for trying Visual Studio 2010 Beta 2 and sending your feedback!

Brittany Behrens

Program Manager, VS Platform - Editor

(bolding above mine for emphasis)

Gee, the team solicited comments, did some research and made a change that people wanted. Of course, any change will make somebody unhappy.

Brittany even volunteered to give folks a simple editor extension to make the settings different for those that want it. My assumption is that anyone using Visual Studio is a developer and capeable of using such an extension, or writing it themselves. It is not difficult.

-Foredecker

Will be fixed...

[nicc777]

Reading the comments on the page leads me to believe that they will eventually fix it, so it will be just a little inconvenient in the beginning.

I see this as the real example of where Open Source development shines - these things would be thrashed out in discussions long before a final release.

On the flip side - no matter what happens in any project, there will always be people who don't like certain features. The only thing that makes this case "special" is that they took away peoples option to set prefer