#1 Command-line option cs don't work

[Anonymous]

In program.cs line:48:

".WithStyleCopSettingsFile(cl.GetOptionValue("s"))" is not correct.

".WithStyleCopSettingsFile(cl.GetOptionValue("sc"))" is correct.
:-)

[Christian K]

I also found out that the -cs command line option doesn't work. I tried changing the line you mentioned and recompiled, but the command line option still doesn't work for me.

Note:
I found out that StyleCopCmd *does* pick up a Settings.SourceAnalysis file that is in the same directory as the .csproj file if one runs StyleCopCmd using the -pf option. However, this might be StyleCop, not StyleCopCmd doing that. StyleCopCmd doesn't pick up the Settings.SourceAnalysis file that is in the same directory as a .cs file when run with the -f option.

[Chris Marlow]

I just found and fixed the same bug! :-) Should have looked here first! lol.

It would be great if a new version could be released with this fix in it (please).

A note to: christiankatict... This fix certainly worked for me. Try debugging in to the
WithStyleCopSettingsFile() call and check the correct file name is being passed through, as what you are reporting sounds like the behaviour I was getting before applying this fix.