Bug 15962 - [regression] Solution-wide code-formatting settings are no longer respected
Summary: [regression] Solution-wide code-formatting settings are no longer respected
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: Trunk
Hardware: All All
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
: 16525 17058 ()
Depends on:
Reported: 2013-11-06 08:53 UTC by Andres G. Aragoneses
Modified: 2014-02-13 05:17 UTC (History)
6 users (show)

Is this bug a regression?: ---
Last known good build:

Screen shot after running "Format Document". (452.43 KB, image/png)
2013-11-07 18:05 UTC, Jason Heddings

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Andres G. Aragoneses 2013-11-06 08:53:52 UTC
Steps to reproduce:
1. Clone banshee source code (http://github.com/gnome/banshee), and open it with MonoDevelop master.
2. (If you right-click on the solution -> Options -> Source Code -> Code Formatting -> C# source code -> you can see that "Convert tabs to spaces" is enabled.)
3. Open any .cs file and write new code.

Current results:
Tabs are added by the IDE.

Expected results:
Spaces should be used.
Comment 1 Jason Heddings 2013-11-07 18:05:56 UTC
Created attachment 5366 [details]
Screen shot after running "Format Document".

I've had the same trouble running XS 4.1.13 (build 17).  I've attached a screen shot showing the visible tabs with the "Convert tabs to spaces" option in the solution code formatting window.  The result is right after running "Format Document" on the open file.
Comment 2 Mike Krüger 2013-11-11 00:59:20 UTC
Comment 3 Jools Adams 2013-11-12 06:27:13 UTC
Do you know what release this fix is or will go in?
Comment 4 Jools Adams 2013-11-12 06:31:26 UTC
Does this bug cover formatting moving all opening braces from the next line up to the end of the previous line? Or would that be considered a separate bug?
Comment 5 Mike Krüger 2013-11-12 09:18:27 UTC
I think 4.2.1
Comment 6 Paul Donovan 2013-11-20 22:21:42 UTC
The opening braces moving to the line above bug is still present in 4.2.1 (build 1). I don't know if there's another bug item for that, but I'd love it to be fixed.
Comment 7 Mike Krüger 2013-11-21 00:41:12 UTC
We don't have a 4.2.1 yet - I fixed that one in master.
Comment 8 Mikayla Hutchinson [MSFT] 2013-11-21 14:51:34 UTC
Unfortunately it wasn't in 4.2.1 - that was an activation hotfix - and it doesn't look like it'll be in 4.2.2 either.
Comment 9 Mike Krüger 2013-11-21 15:32:07 UTC
btw. the opening braces thing from the support forum is unrelated to that one.
Comment 10 Jools Adams 2013-11-21 16:03:25 UTC
What's the opening braces thing, and do you have a bug # for it?
Comment 11 Mike Krüger 2013-11-21 23:38:45 UTC
no - it's in the forums it's a missing option how anonymous methods should be formatted as parameters.
Comment 12 Mikayla Hutchinson [MSFT] 2013-11-30 17:09:49 UTC
*** Bug 16525 has been marked as a duplicate of this bug. ***
Comment 13 Mike Krüger 2014-01-06 02:32:55 UTC
*** Bug 17058 has been marked as a duplicate of this bug. ***
Comment 14 Mike Krüger 2014-02-04 02:02:59 UTC
*** Bug 17548 has been marked as a duplicate of this bug. ***
Comment 15 Jools Adams 2014-02-12 03:58:18 UTC
Does anyone know if this bug fix is in 4.2.3?
Comment 16 Mike Krüger 2014-02-12 04:30:44 UTC
I think it's in 4.2.4 - it'll hit the alpha channel *soon* if it hasn't already.
Comment 17 Jools Adams 2014-02-13 05:17:04 UTC
Hmm ... the alpha channel seems to be at 4.3.2. The beta channel is at 4.2.3.