IDE options to control the sorting of fields and properties

[conniey]

Steps to Reproduce

1. Create a WPF Application
2. Open MainWindow.xaml.cs
3. Type the following: string field;

    public partial class MainWindow : Window
    {
        string field;

        public MainWindow()
        {
            InitializeComponent();
        }
    }

1. Press Ctrl+.
2. Select "Encapsulate field: 'field' (usages reference field)" and press Enter

Expected
Behaviour in VS2013

Actual

1. Field is generated at the bottom of the class declaration (sometimes it is generated in the correct location though.. right below the field declaration)
2. Unnecessary new lines are added to the getter/setter
   

[Pilchie]

The newlines are also tracked by http://connect.microsoft.com/VisualStudio/feedback/details/1617595/incorrectly-formats-source-code-when-using-the-encapsulate-field-command.

The property placement may be by design, but we should understand the difference.

[rchande]

The newline aspect of this is tracked by #84.

[rchande]

Generally, Roslyn inserts properties after constructors, as controlled by the CSharpDeclarationComparer. We'll use this bug to track adding options to modify that sort order.

[galastur]

Really annoying all those extra lines when generating the get/set for a property...please let us have it as it was with VS 2013 !!!

[Pilchie]

Note - when implementing, it would probably be a good idea to re-use the idea of Symbol Specification from naming styles to define this ordering.

[CyrusNajmabadi]

I don't repro this. The fields go in teh right place, and the property formatting is correct.