StyleCop Updates and Run StyleCop as part of your Team Build

Version 4.3.1 contains the following fixes and updates over 4.3.0:

• Ability to use <include> tags within Xml documentation headers
• Fixes crash and instability on Web projects
• Violations can appear within generated code regions
• Setup slowness when registering with VS2008
• Partial methods not handled correctly
• Documentation rules should understand <include> element
• Require get accessor before set accessor
• When documenting a generic class, only allows <see cref="MyClass"/> and not <see cref="MyClass`1"/>
• Analysis of files in websites crashes Visual studio 2005 and 2008
• SA1623 and SA1624 warnings appears in wrong situations
• ‘using’ statement does not require curly brackets
• Class without explicit access modifier marked as "public" instead of "internal"
• False warning: SA1119: The line contains unnecessary parenthesis
• Ignore .generated.cs files
• Style Cop Crashes With A Blank Definition File
• SA1101 isn’t raised in method calls when the return value of the method is used.
• VS crashed for webservices.
• False syntax error with a nullable generic type reference.
• LINQ operator "let" cause SA0101 when used with "condition ? true : false" syntax
• False syntax error with a defaulted array

You can download the new version of StyleCop here.  NOTE: you must uninstall the old version to install this one.  If you want to integrate StyleCop with MSBuild go and have a look at this blog posting.

If you are interested in getting StyleCop to work with Team Build, I suggest you checkout this blog posting by Richard Fennel.