Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add StyleCop.MSBuild #44

Closed
adamralph opened this issue Feb 10, 2013 · 2 comments
Closed

Add StyleCop.MSBuild #44

adamralph opened this issue Feb 10, 2013 · 2 comments
Assignees

Comments

@adamralph
Copy link
Contributor

https://nuget.org/packages/StyleCop.MSBuild/

We can also add

<StyleCopTreatErrorsAsWarnings>false</StyleCopTreatErrorsAsWarnings>

in the csproj files if we want to enforce compliance.

@philippdolder
Copy link
Member

I agree. Using StyleCop in all my customer's projects. But we need to tweak the settings a bit. I don't want comments to be enforced for example.

@adamralph
Copy link
Contributor Author

My usual preference for an API is to enforce documentation for public members but not for internals and privates but I'm happy to go with the consensus. If there are a lot of public members currently missing documentation then this is not practical in the short term anyway.

@ghost ghost assigned adamralph Feb 22, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants