I see that nant.project.basedir
is deprecated.
What is the best way to get at this information?
I need to pass a comma separated list of fully qualified
paths to assemblies to Vil…
Thanks,
steve
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jim Geurts
Sent: Tuesday, July 12, 2005 8:16
AM
To: Foster, Richard - PAL; James
Jackson; nant-users@lists.sourceforge.net
Subject: Re: [Nant-users] FxCop
failing build
James,
I'm not sure if you're using the fxcop task (part of NAntContrib) or just
calling fxcopcmd.exe. If you are using the task, I would think you could
just set the "directOutputToConsole" attribute to true. That
way the output would be added to the NAnt report. Otherwise there is a
related flag you could add when you call fxcopcmd.exe to do the same.
Jim
On 7/12/05, Foster,
Richard - PAL <[EMAIL PROTECTED]>
wrote:
James,
You may find that the latest version of FX-Cop (1.32, released July 1st)
does return error codes... or at least it seems to for me, because my
build started to fall over when I switched to the new version!
I also assume that if you were running a pre 0.9.1 release you moved the
"merge" tasks into the "publishers" section as mentioned in
the release
notes? If not, then the merge operations would never be triggered (as
you describe).
Regards,
Richard
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:
[EMAIL PROTECTED]] On Behalf Of James
Jackson
Sent: Tuesday, July 12, 2005 07:37
To: nant-users@lists.sourceforge.net
Subject: [Nant-users] FxCop failing build
Hi there,
I'm trying to integrate FxCop as part of our build process. We have a
shared build script that developers run locally, and that our continuous
integration server runs. As FxCop does not return failure error codes,
I've implemented the method recommended by MS, in that if after analysis
there's a report XML file, fire off the Nant <fail> task. This is fine
when our build script is run locally, however, on our CI server (running
CC.Net), this seems to fail the build in a very
terminal way, so the
output XML files don't get merged in the CC.Net
<merge> task. Not too
hot if the developer can't see what's failing the build on the CI
server!
Can anyone suggest a workaround for this? I could knock up a quick
standalone app, and call it with the CC.Net
<exec> task, but I don't
know if I can use status return codes to fail the build from there - the
documentation isn't too hot.
Cheers,
James.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With
Dual!' webinar
happening July 14 at 8am PDT/11am EDT. We invite you to explore the
latest in dual core and dual graphics technology at this free one hour
event hosted by HP, AMD, and NVIDIA. To register visit
http://www.hp.com/go/dualwebinar
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With
Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
