StyleCop

Thanks a lot for this tool!

Where is the promised version 4.3 that fixes the "COM object detached from RCW" error?

When will Visual Studio generated code such as for unit tests be StyleCop compliant?

We are currently finalizing the documentation for the 4.3 release and will get this release out to you as soon as we can get the docs published. Thanks for your patience.

If the 4.3 has passed testing can we have it as install now? The inability of 4.2 to co-exist with ReSharper is major problem. Can you also give a copy of 4.3 to people at JetBrains so they can test it against ReSharper .

StyleCop 4.3 has now been released on this site.

There is a problem in upgrading from 4.2 to 4.3 in that only one version can be installed. The build path has changed in the project file from
<Import Project="$(ProgramFiles)\MSBuild\Microsoft\SourceAnalysis\v4.2\Microsoft.SourceAnalysis.targets" />
</Project>
to
<Import Project="$(ProgramFiles)\MSBuild\Microsoft\StyleCop\v4.3\Microsoft.SourceAnalysis.targets" />
</Project>

This requires a manual edit of the project file as it will not load until this path is modified.

@TATWORTH
Please use the "Discussions" or issues tab above for these kind of comments.

Woow, this is very very cool. The style it enforces is great and I'm going to force my colleage developers with a bad coding style to use this.

FYI - StyleCopCmd was released last week at http://stylecopcmd.sourceforge.net/. StyleCopCmd provides a command line interface and NAnt task for interacting with StyleCop. StyleCopCmd also creates beautiful HTML reports, making it easy to integrate with continuous integration servers such as TeamCity.

Great tool.. Just superb... :-)

Someone mentioned wanting a VB Version. I'd like to see a VB Version that not only changes the style but converts the VB to C#! Wish VB never existed

@ daveschinkel
I am one of those, who want a VB Version! With quite the same right (actually NO right at all!) I could say the same thing about C#

@ MSFT
I think it is an affront for all the millions of VB developpers, that so far not even an announcment has been made about a VB version.

any word on VB version? I'd definitely vote for a feature request.

I have to step back from my previous comment, because jasonall has given a very detailed explaination of the problems with a VB version, and an outlook in things to come. See http://code.msdn.microsoft.com/sourceanalysis/Thread/View.aspx?ThreadId=383 for details!

Again, thanks jasonall!

Does StyleCop work with all versions of Visual Studio (2003, 2005, 2008) ?

I think I found a defect. If my class has a property, and my class uses an object that has a property of the same name, StyleCop prompts me that my use of that property should begin with this. when it should not (it must begin with a reference to that object).

When is the website analysis fix going to be released? This is causing a right pain.

@TheRubble: Web project issues have been fixed in 4.3.1.3, available now.

@Dtinney: StyleCop 4.3 integrates into VS 2005 or newer.

Thank you for that tool!

I love this tool; and paired with StyleCop for ReSharper, this is just awesome.

thank you very very much. really good tool

We need a stylecop for C++ code as well. Do you have plans to develop one such tool/add that feature?

Open sourcing StyleCop is a really really good idea. Thx guys.

Feature request: provide a "fix it" function to let the user select all of the Stylecop warnings and fix in one scoop.

This tool is very interesting.
One question: how can we access to assembly attributes?
I searched many hours and not found the solution.
We have to use Token collection to search "Assembly" token?
Thanks for your response.

Great tool!

BUT...I'm running it against Massive (https://github.com/robconery/massive) and it erroneously reports a syntax error as a warning where the compiler reports no such error. The warning is:

Warning 1 SA0102: A syntax error has been discovered in file C:\Users\a7247\Documents\Visual Studio 2010\Projects\Massive Kata\Massive\Massive.cs on line 24. C:\Users\a7247\Documents\Visual Studio 2010\Projects\Massive Kata\Massive\Massive.cs 24 1

Forgot to mention, line 24 in my source file is the signature of the constructor for the DynamicModel class:

public DynamicModel(string connectionStringName = "", string tableName = "", string primaryKeyField = "")