Hi

did you check a build log file in the artifact folder?
if you open it with notepad, do you see any information that points to
StyleCop?

this is the fisrst step that must be done, get the stylecop information into
the buildllog.
When this is done, we must see to get it in  the dasboard.


with kind regards
Ruben Willems


On Thu, Jan 8, 2009 at 4:02 PM, MBRDBJ <[email protected]> wrote:

>
> Hi Ruben and thanks for answering so quickly.
>
> I know MSBuild supports StyleCop but does so totally independent from
> CC.Net.
>
> This is what I have so far. I have integrated StyleCop and it should
> run automatically every time the build is ran onto my project. It does
> that, and I can see the results in the Visual Studio's error list ....
> 0 errors, 1250 warnings.
>
> Interestingly enough, when I try to force a build through CC.Net I get
> an information that the build was successful and that there were: 0
> errors and 3 (???) warnings. Below that, it lists those three warnings
> and all three of them are in the mold, 'that variable was assigned but
> is never used'.
>
> As a last resort I have changed the csproj file to get every StyleCop
> warning as an actual error with hopes that it will break my CC.Net
> build, and still nothing. I get the same results as before: 0 errors,
> 3 warnings. It's like CC.Net ignores every error/warning triggered by
> StyleCop.
>
> ?

Reply via email to