RE: [ccnet-user] there must be some change to the exec task in 1.6

[Craig & Sammi Sutherland]

And the documentation has been updated for the package - it was not being
included in the automatic updates so I have manually updated it.


Craig

-----Original Message-----
From: ccnet-user@googlegroups.com [mailto:ccnet-user@googlegroups.com] On
Behalf Of östen petersson
Sent: Monday, 31 January 2011 8:18 p.m.
To: ccnet-user
Subject: [ccnet-user] there must be some change to the exec task in 1.6

so the below snippets has worked in 1.4 and 1.6 I did an upgrade
before the weekend and now all projects running fxcop is failing

the message is as always with fxcop cryptic:

<buildresults>
  <message level="Error">Argument specified without a corresponding
switch : '</message>
  <message level="Error">'.</message>
  <message level="Error">Type FxCopCmd.exe /? for help on command-line
arguments.</message>
</buildresults>



<cb:define name="fxcopspecificArgs">
      /file:$(WorkingDirectory)$(MyProject)
\blabla.Common.Wcf.CommitteeServiceCore.dll
      /directory:$(WorkingDirectory)$(MyProject)\Test\bin\Build\
      /out:"$(ServerDictionary)$(MyProject)$(myProjectType)\Artifacts
\fxcopreport.xml"
      /project:"$(WorkingDirectory)config_filer\fxcopfiles
\basic.FxCop"
      /dictionary:"$(fxcopDictionary)"
      /quiet
      /timeout:90
      /ignoregeneratedcode
      /ignoreinvalidtargets
      /forceoutput
      /verbose
      /searchgac
    </cb:define>


          <exec>
            <description>............running fxcop............</
description>
            <executable>D:\ccnet_tools\fxcop\FxCopCmd.exe</executable>
            <buildArgs>
              <cb:fxcopspecificArgs/>
            </buildArgs>
            <buildTimeoutSeconds>900</buildTimeoutSeconds>
          </exec>

since my brain shuts down every time I stare at xml I have a hard time
figuring out whats wrong - anyone with a tip?

also you are going to update the documentation on the packager syntax
right?