StyleCop settings


Move settings to project file and move settings editor to project properties pages range.
Closed Nov 29, 2016 at 5:30 AM by csdahlberg
Closing this work item due to its age and because development is moving to GitHub. Please open a new issue at https://github.com/StyleCop/StyleCop if this still needs to be addressed.


AArnott wrote Aug 22, 2011 at 4:20 PM

Downvote. Project files should only contain settings that impact the built binary.

davedev wrote Dec 9, 2012 at 4:51 PM

@AArnott: What makes you say that? Do you have any reference to the official documentation stating that project files are not intended for static analysis settings? Other static analysis tools add their settings to the project file; e.g., Code Analysis (FxCop) and Code Contracts. (Though in fairness, Code Contracts also has a runtime component.)

davedev wrote Dec 9, 2012 at 4:53 PM

@AArnott: Furthermore, StyleCop does have an affect on the built binary - after you fix your code to make the warnings go away. So perhaps it's just a deferred effect, but it's an effect nonetheless.