What rules should StyleCop use when writing an open source library

I am currently writing an open source wrapper for a COM object. I just installed StyleCop and ran it against some of my code, and, as I expected, it started loading warnings (some of which I had to do, for example, adding “this” to all calls and variables of local methods)

How many of these warnings should I try and reduce? Which ones would be best when writing an open source library?

+5
source share
2 answers

General idea with StyleCop: all of them :)

, StyleCop - . , , , , StyleCop , , , .

, StyleCop, , , , .

, , FxCop , StyleCop.

+5

. , Apache C.

FAQ , , .

, , , , !; -)

, - . " " ( ), !

: , , . . , , - . , " " ( Amazon - script , ).

, " ", - ! (-:

.

,

Rob

0

All Articles