But if the StyleCop settings override that setting, the new StyleCop values will win, because they have a higher priority than the defaults. So, setting something to be the default value will not write the default value to globals, and ReSharper will just use the value from the defaults. However, ReSharper is "smart" when it comes to saving - roughly speaking, if the value you're setting is the same as in a lower layer, it simply removes it from the current layer. The StyleCop settings shouldn't override any layers that you've already got mounted, as they're set to have a priority lower than globals, and anything you've changed will be saved to the global layer. This removes any overriding settings from the global and per-solution layers. You can reset the settings back to the StyleCop defaults by going to the StyleCop options page, and clicking Reset Settings. So, if you've already set any of these settings, your modifications take precedence (because they live in the higher priority global or per-solution layers). More technically, the StyleCop settings file is mounted as a layer, above the defaults, but below the global (and per-solution) levels. In a clean install, this means StyleCop overrides ReSharper's default settings. However, doing so might conflict with existing StyleCop rules, in which case, disable the StyleCop rules in The way the settings work is to ship the StyleCop settings in a settings file that is merged with ReSharper's defaults. This project doesn't do anything to support StyleCop+, but looking at the site, it looks like most of the features are already available in ReSharper - you can configure ReSharper to set different naming conventions for different types of entity - classes, interfaces, fields, etc.
#Resharper 9 update install
I believe has a package of the last released set of rules - StyleCop.MSBuild, or if you're using Visual Studio 2015, you can use the new StyleCop.Analyzers package to install Roslyn analysers. This project doesn't have an msbuild package.StyleCop files and open them in a nice settings editor.
You can still install the standard StyleCop distribution, which will set up a file association for the. There isn't a settings editor right now, so you pretty much need to know the XML format - more details are available on the original CodePlex site.
As I understand it, you can also place a copy next to the file being analysed, and at any folder up to the root of the solution. Getting very close to releasing it to the You need to add Settings.StyleCop to the root of the solution. I think that's it, but there could be more.