Dave Grochocki

Thanks for the suggestion! I created #44 to capture discussion on this issue, since it seems different enough to be considered an independent feature from blocked elements.

If you want to use this in CI, I assume your primary goal is for the CLI version of XAML Styler to respect this new proposed setting? I am curious...

_Should_ be safe to update ```CompareNETObjects``` but there are gotchas with ```Newtonsoft.Json```. Updating can lead to unexpected behavior on older versions of Visual Studio (#242). More information here: [Using Newtonsoft.Json...

While we have done something similar with VisualStateManager, this may be trickier. A few open questions: * Can we leverage the same attribute ordering setting? * Do we need a...

Thanks for the bug report! This is currently by design, since XAML Styler will either (a) look for Visual Studio indent options or (b) rely on [Indent Size](https://github.com/Xavalon/XamlStyler/wiki/External-Configurations#indent-size) in a...

Thanks for the detailed write up! We think this is a great idea, but there are a couple open questions we want to think through before implementing this: * How...

> Project1.xaml should be formatted according to **setting 2**, but **setting 1** is used currently. I would expect Project1.xaml, in this case, to be formatted via **setting 1**, since it...

> Alternatively, put your external configuration inside a "Settings.XamlStyler" file in any directory **up through your solution directory** and this configuration will take precedence. The documentation does not make it...

> How about this priority rule? @tmatz I agree with the hierarchy here, but I don't think @schlotter's interpretation is quite right. The "closest" configuration in the up-hierarchy should take...

> In this example, the solution directory is not in a up-hierarchy of any .xaml file. And, there is **setting 1** which is in up-hierarchy of all .xaml files. So...