Are External Configurations in options handled as you would expect? about xamlstyler HOT 2 CLOSED

I can try to sum up my view:

Foo.sln
Foo.sln.xamlstyle
  Bar.csproj
  Bar.csproj.xamlstyle

With the following resolution precedence:
1 *.csproj.xamlstyle
2 *.sln.xamlstyle
3 Other settings file specified in plugin settings
4. Default plugin settings.

When thinking about it I can't think of a case where per project style makes sense.

Having the settings with the code is nice as it allows the settings to be version controlled keeping a team in sync. This is a huge feature as different settings around a team would create a diff nightmare.

Naming settings *.sln.xamlstyle makes it easy to find and follows the convention r# uses.

from xamlstyler.

There has not been enough feedback to indicate that we should change from the current behavior, so we will be closing this issue for now. Please feel free to reactivate it if new conversation is warranted.

from xamlstyler.