I am a big fan of Stylecop and I always follow it guidelines. I also follow the guideline that state that a comment should bring added value to the code and not repeat what the code is doing.
Some problems that I recall (there may be more): Includes regions Does not use this. prefix for me开发者_运维问答mber variables and methods
These 3 types of lock are apparently bad. What other type of locking is bad? Are there Stylecop / FxCop rules that would catch this?
Dinking around with stylecop settings files is getting annoying and messing with my repo structure. The repo is like this:
We are seeing extremely strange results where StyleCop will correctly report violations when run from within Visual Studio 2010.However, when开发者_高级运维 we run msbuild on the command line (e.g., \
Our team is still in a love / hate relationship with it. I am hoping to put an end to the debate by having an internal vote on what rules should be excluded and which rules should be added.
The related default StyleCop rules are: Place using statements inside namespace. Sort using statements alphabetically.
So here\'s the problem.I\'m writing some StyleCop plug-in assemblies for use at the company I work for.As such, these assemblies need to reference Microsoft.StyleCop.CSharp.dll for example, which is s
I opened up a huge Solution in VS2008. I has about a little over a thousand style cop warnings. I don\'t have resharper or any other commercial visual studio add-ins. Is there any way I can filter the
I am trying to suppress the following StyleCop message for a specific property: SA1513: Statements or elements wrapped in curly brackets must be followed by a blank line.