Re: [NAnt-users] ant condition task equivalent in NAnt

[Bob Archer <Bob.Archer@am...>]

4.1 Operator precedence

NAnt expressions support standard ( c style ) operator precedence, that we're accustomed to:

 *   and is evaluated before or, left to right. For example false or true and true and false evaluates as false or ((true and true) and false)
Perhaps you can show us the expression you are using and we can help you out a bit more.

BOb


________________________________
From: Munawar Rashid [mailto:a_m_rashid@...]
Sent: Wednesday, May 27, 2009 11:34 AM
To: Bob Archer; nant-users@...
Subject: RE: [NAnt-users] ant condition task equivalent in NAnt

Thx for your reply. I couldn't find any example on it in the net. I also couldn't find anything in NAnt task catalog. Does anybody know where I can find this info.

________________________________
From: Bob.Archer@...
To: a_m_rashid@...; nant-users@...
Date: Tue, 26 May 2009 15:19:20 -0400
Subject: RE: [NAnt-users] ant condition task equivalent in NAnt
Sure you can.

________________________________
From: Munawar Rashid [mailto:a_m_rashid@...]
Sent: Tuesday, May 26, 2009 1:43 PM
To: nant-users@...
Subject: [NAnt-users] ant condition task equivalent in NAnt


Is this available to check whether multiple conditions are being met (through 'or'-ing and 'and'-ing of the conditions). I know its in Ant.

Thx

Re: [NAnt-users] ant condition task equivalent in NAnt

[Munawar Rashid <a_m_rashid@ho...>]

Thx for your reply. I couldn't find any example on it in the net. I also couldn't find anything in NAnt task catalog. Does anybody know where I can find this info.
 


From: Bob.Archer@...
To: a_m_rashid@...; nant-users@...
Date: Tue, 26 May 2009 15:19:20 -0400
Subject: RE: [NAnt-users] ant condition task equivalent in NAnt









Sure you can.
 





From: Munawar Rashid [mailto:a_m_rashid@...] 
Sent: Tuesday, May 26, 2009 1:43 PM
To: nant-users@...
Subject: [NAnt-users] ant condition task equivalent in NAnt
 
 
Is this available to check whether multiple conditions are being met (through 'or'-ing and 'and'-ing of the conditions). I know its in Ant.
 
Thx

 

Re: [NAnt-users] ant condition task equivalent in NAnt

[Bob Archer <Bob.Archer@am...>]

Sure you can.

________________________________
From: Munawar Rashid [mailto:a_m_rashid@...]
Sent: Tuesday, May 26, 2009 1:43 PM
To: nant-users@...
Subject: [NAnt-users] ant condition task equivalent in NAnt


Is this available to check whether multiple conditions are being met (through 'or'-ing and 'and'-ing of the conditions). I know its in Ant.

Thx

[NAnt-users] ant condition task equivalent in NAnt

[Munawar Rashid <a_m_rashid@ho...>]

 

Is this available to check whether multiple conditions are being met (through 'or'-ing and 'and'-ing of the conditions). I know its in Ant.

 

Thx


 

Re: [NAnt-users] nant and resgen.exe

[Gert Driesen <gert.driesen@te...>]

Hey Raj,

I assume you're using NAnt 0.85, as this was fixed since.
I suggest to try the latest nightly build:
http://nant.sourceforge.net/nightly/latest/

Hope this helps,
Gert

-----Original Message-----
From: ptr2009 [mailto:ptrajkumar@...] 
Sent: dinsdag 19 mei 2009 22:54
To: nant-users@...
Subject: [NAnt-users] nant and resgen.exe


hey all

   When compiling against mono-3.5 profile on MacOS X I have noticed that
regsen.exe that gets used is from 1.0 directory
(Mono.framework//Versions/2.4/lib/mono/1.0/resgen.exe)  and not 2.0
directory. 

   Copying the resgen.exe from 2.0 directory to 1.0 directory fixes this
problem ?

Is this is known issue and if so is there a better fix ?

Thanks
Raj
-- 
View this message in context:
http://www.nabble.com/nant-and-resgen.exe-tp23623978p23623978.html
Sent from the NAnt - Users mailing list archive at Nabble.com.


----------------------------------------------------------------------------
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
NAnt-users mailing list
NAnt-users@...
https://lists.sourceforge.net/lists/listinfo/nant-users

No virus found in this incoming message.
Checked by AVG - http://www.avg.com 
Version: 8.5.285 / Virus Database: 270.12.32/2119 - Release Date: 05/17/09
16:58:00

[NAnt-users] nant and resgen.exe

[ptr2009 <ptrajkumar@gm...>]

hey all

   When compiling against mono-3.5 profile on MacOS X I have noticed that
regsen.exe that gets used is from 1.0 directory
(Mono.framework//Versions/2.4/lib/mono/1.0/resgen.exe)  and not 2.0
directory. 

   Copying the resgen.exe from 2.0 directory to 1.0 directory fixes this
problem ?

Is this is known issue and if so is there a better fix ?

Thanks
Raj
-- 
View this message in context: http://www.nabble.com/nant-and-resgen.exe-tp23623978p23623978.html
Sent from the NAnt - Users mailing list archive at Nabble.com.

Re: [NAnt-users] <call> task with parameters ...

[Richard Brown \(GMail\) <flukefan@go...>]

 I think the macro-def task looks like a much nicer syntax, and it would be nice to mirror Ant if it has the same thing already.

(Wish I'd noticed this when I wrote NAntScript)


From: Richard Brown (GMail) 
Sent: Thursday, May 14, 2009 1:25 PM
To: Bjerstedt, Tony [Audatex - Americas] ; Bob Archer ; Gert Driesen ; Parrish, Ken ; nant-users@... 
Subject: Re: [NAnt-users] <call> task with parameters ...



Hi all,

I think this would be a great addition to the core functionality of NAnt.

I had previously done something similar, but it was a bit hacky:
http://nant.sourceforge.net/external.html#nantscript

Most of the hacks revolved around the ability to not just pass in regular parameters, but also complete sections of custom XML.  I'm not sure it there's a nice way to do this (and it tends to make the schema checking of NAnt screw up), but it would be excellent if it could be handled in a more elegant way by the core engine.

e.g., In addition to the ability to call a target like:

            <call target="name">

              <with-parameter name="param1" value="."/>

              <with-parameter name="param2" value="."/>

               .

            </call>


... you might want to call a target with a complex parameter type like:

            <call target="name">



              <with-parameter name="param1">

                <include name="*.myFiles"/>

                <exclude name="*.notMyFiles"/>

              <with-parameter/>



              <with-parameter name="param2">

                <include name="*.myResourceFiles"/>

              <with-parameter/>

               .

            </call>


Regards,
    Richard




From: Duncan Godwin 
Sent: Thursday, May 14, 2009 9:45 PM
To: Bjerstedt, Tony [Audatex - Americas] ; Parrish, Ken ; nant-users@... 
Subject: Re: [NAnt-users] <call> task with parameters ...


Hi

I came across this task a while ago and looks like a good fit though I haven't tried it myself:
http://www.markhneedham.com/blog/2008/08/14/macros-in-nant/

Cheers

Duncan
  ----- Original Message ----- 
  From: Bjerstedt, Tony [Audatex - Americas] 
  To: Parrish, Ken ; nant-users@... 
  Sent: Wednesday, May 13, 2009 7:00 PM
  Subject: Re: [NAnt-users] <call> task with parameters ...


  I have wondered the same thing. If this were added, I would suggest an approach similar to XSLT.

   

  An XSLT like approach would look something like:

   

              <call target="name">

                <with-parameter name="param1" value="."/>

                <with-parameter name="param2" value="."/>

                 .

              </call>

   

  and 

              <target name="name">

                <parameter name="param1" default="value"/>

                <parameter name="param2" />

                .

              </target>           

   

  A couple of years ago I started playing with this type of approach.

   

   

  From: Parrish, Ken [mailto:KParrish@...] 
  Sent: Wednesday, May 13, 2009 10:56 AM
  To: nant-users@...
  Subject: [NAnt-users] <call> task with parameters ...

   

  Has there ever been any consideration to creating a mechanism for executing the <call> task with a set of private, local parameters (properties) which are only available inside the called task?

   

  I'm not sure exactly how the syntax would work, but the idea would be to pass, as an argument to the <call> task, a list of name/value pairs, or a list of values that are identified by place or order.

   

  I find the I often need to fabricate some sort of parameter passing mechanism, using globally defined <properties> , to control <task>s that are designed to be general purpose.  Typically, I'll create <property> elements that have names which include the name of the task:

   

                  <property name="mytask_sourceDir" value="sourceValue" />

                  <call task="mytask" />

   

  I'd much prefer something like:

   

                  <call task="mytask" parameters="sourceDir=sourceValue" />

   

  The assumption would be that the parameter 'sourceDir' is visible only inside 'mytask'.

   

  Thoughts, ideas, considerations?

   

  Ken Parrish

  Gomez, Inc.

   

   

Re: [NAnt-users] <call> task with parameters ...

[Duncan Godwin <duncangodwin@di...>]

Hi

I came across this task a while ago and looks like a good fit though I haven't tried it myself:
http://www.markhneedham.com/blog/2008/08/14/macros-in-nant/

Cheers

Duncan
  ----- Original Message ----- 
  From: Bjerstedt, Tony [Audatex - Americas] 
  To: Parrish, Ken ; nant-users@... 
  Sent: Wednesday, May 13, 2009 7:00 PM
  Subject: Re: [NAnt-users] <call> task with parameters ...


  I have wondered the same thing. If this were added, I would suggest an approach similar to XSLT.

   

  An XSLT like approach would look something like:

   

              <call target="name">

                <with-parameter name="param1" value="."/>

                <with-parameter name="param2" value="."/>

                 .

              </call>

   

  and 

              <target name="name">

                <parameter name="param1" default="value"/>

                <parameter name="param2" />

                .

              </target>           

   

  A couple of years ago I started playing with this type of approach.

   

   

  From: Parrish, Ken [mailto:KParrish@...] 
  Sent: Wednesday, May 13, 2009 10:56 AM
  To: nant-users@...
  Subject: [NAnt-users] <call> task with parameters ...

   

  Has there ever been any consideration to creating a mechanism for executing the <call> task with a set of private, local parameters (properties) which are only available inside the called task?

   

  I'm not sure exactly how the syntax would work, but the idea would be to pass, as an argument to the <call> task, a list of name/value pairs, or a list of values that are identified by place or order.

   

  I find the I often need to fabricate some sort of parameter passing mechanism, using globally defined <properties> , to control <task>s that are designed to be general purpose.  Typically, I'll create <property> elements that have names which include the name of the task:

   

                  <property name="mytask_sourceDir" value="sourceValue" />

                  <call task="mytask" />

   

  I'd much prefer something like:

   

                  <call task="mytask" parameters="sourceDir=sourceValue" />

   

  The assumption would be that the parameter 'sourceDir' is visible only inside 'mytask'.

   

  Thoughts, ideas, considerations?

   

  Ken Parrish

  Gomez, Inc.

   

   


  - ---------------------------------------------------------------------------



  PRIVILEGE AND CONFIDENTIALITY NOTICE
  The information in this electronic mail (and any associated attachments) is intended for the named recipient(s) only and may contain privileged and confidential information. If you have received this message in error, you are hereby notified that any use, disclosure, copying or alteration of this message is strictly prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy all copies of the original message. Thank you.



  - --------------------------------------------------------------------------



------------------------------------------------------------------------------


  ------------------------------------------------------------------------------
  The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
  production scanning environment may not be a perfect world - but thanks to
  Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
  Series Scanner you'll get full speed at 300 dpi even with all image 
  processing features enabled. http://p.sf.net/sfu/kodak-com


------------------------------------------------------------------------------


  _______________________________________________
  NAnt-users mailing list
  NAnt-users@...
  https://lists.sourceforge.net/lists/listinfo/nant-users

Re: [NAnt-users] Problem with pkg-config finding mono

[ptr <ptrajkumar@gm...>]

I see the same problem in the latest download of mono 2.4 on mac. Adding
/Library/Frameworks/Mono.framework/Versions/2.4/bin to PATH seems to resolve
the issue for me

Raj

On Fri, Apr 24, 2009 at 7:47 AM, Gert Driesen <gert.driesen@...>wrote:

>  Hi Ron,
>
> From the error it's clear that NAnt cannot start pkg-config.
> Perhaps you should try to create a small test app that launches pkg-config
> using the System.Diagnostics.Process class, to rule out a mono related bug.
> If you have any problem creating this app, then just let me know.
>
> Gert
>
>  *From:* Ron Grove <ron.grove@...>
> *Sent:* Friday, April 24, 2009 5:58 AM
> *To:* nant-users@...
> *Subject:* Re: [NAnt-users] Problem with pkg-config finding mono
>
> I'm on a different OS X computer now (my wife's iMac) and I downloaded Mono
> and Monobjc and get the same error from Nant.  I tried the small test build
> file in this post:
> http://www.mail-archive.com/nant-users@.../msg04071.html
>
> That recommends a small test build file containing:
>
> <project name="pkg-config-test">
>  <echo message="mono prefix: ${pkg-config::get-variable('mono', 'prefix')}" />
>  <echo message="exists mono: ${pkg-config::exists('mono')}" />
>  <echo message="modversion mono: ${pkg-config::get-mod-version('mono')}" />
>
> </project>
>
> But get the same error.  Both computers seem to see that mono is there.
>  --exists mono doesn't give an error.  It's in the --list-all output, etc.
>  The mono version seems fine:
>
>  debora:bin Ron$ ./pkg-config --modversion mono
> 2.4
>
> I tried running nant with --debug and it doesn't really tell me anything
> more.  I'm lost.
>
> Thank you,
> Ron
>
>
>  On Apr 23, 2009, at 4:52 PM, Ron Grove wrote:
>
>  I'm having trouble with pkg-config when I run nant on the monobjc
> project's package, but others have it working fine.  The email below details
> what I've done so far from a different mailing list.  I really don't
> understand why pkg-config says it can't find mono.  When I run the command
> on its own with --list-all it does list mono.  I'm not sure how the --exists
> switch is to be used, though.  Just putting mono after it doesn't give me
> anything, but when I run it with --debug it says the value of --print-errors
> is 0.  I expect that's good.  When I use the --libs switch it gives me
> plenty of info.  The mono.pc file is in the /Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig
> folder.  Any ideas about why it keeps failing on me with the error:
> Expression: ${not pkg-config::exists('mono')}
> Thank you,
> Ron
>
>
> Begin forwarded message:
>
>  *From: *Ron Grove <ron.grove@...>
> *Date: *April 23, 2009 4:16:07 PM PDT
> *To: *users@...
> *Subject: **Re: [users@...] Problem building samples*
> *Reply-To: *users@...
>
> Interestingly I can run and run the command
>
> /Library/Frameworks/Mono.framework/Commands/pkg-config --list-all
>
> and mono is in the list it outputs.  Man that's irritating...
>
>
> On Apr 23, 2009, at 4:04 PM, Ron Grove wrote:
>
> I'm not completely sure what you mean by cleaning up my setup.  The XCode
> 3.1 tools are installed and work fine for Objective-C projects.  I need
> those tools so uninstalling them isn't really something I want to do unless
> there's a reason.  nant seems to be installed correctly:
>
>
> ron:~ ron$ nant -help
>
> NAnt 0.86 (Build 0.86.2898.0; beta1; 12/8/2007)
>
>
> ron:~ ron$ whereis nant
>
> /usr/bin/nant
>
>
> ron:~ ron$ ls -l /usr/bin/nant
>
> lrwxr-xr-x  1 root  wheel  48 Apr 10 15:11 /usr/bin/nant ->
> /Library/Frameworks/Mono.framework/Commands/nant
>
>
> Still not sure why, but it's this pkg-config::exists function that's
> failing to find mono.  But I can run it fine from the command line and it's
> in my path.  Suppose I'll have to sign up on their mailing list and ask.  I
> was just hoping someone else may have run into it here.
>
>
> -Ron
>
>
>
>  2009/4/17 Ron Grove <ron.grove@...>:
>
>  I've tried to built the samples using nant and get this error message
> below.
>
>  I've never used it before and not sure what to do.  This page doesn't
> tell
>
>  me much:
>
>
>
> http://nant.sourceforge.net/release/0.85-rc1/help/functions/pkg-config.exists.html
>
>
>  Where is it looking for the package?  I have the latest download for OS X
>
>  installed on the system.  All the old versions are gone so far as I can
> see.
>
>  Somewhere I read to set $PKG_CONFIG_PATH
>
>  to /Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig
> which
>
>  I've done, but that didn't help.  Any ideas?
>
>
>  Thank you,
>
>  Ron
>
>
>  -------------------------------------------
>
>
>  BUILD FAILED
>
>
>  Failed to initialize the 'Mono 3.5 Profile' (mono-3.5) target framework.
>
>
>   Function call failed.
>
>  Expression: ${not pkg-config::exists('mono')}
>
>                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>
>       'pkg-config' failed to start.
>
>
>           ApplicationName='pkg-config', CommandLine='--exists mono',
>
>
> CurrentDirectory='/Library/Frameworks/Mono.framework/Versions/2.4/share/NAnt/bin/'
>
>
>  For more information regarding the cause of the build failure, run the
> build
>
>  again in debug mode.
>
>
>
>
>
>
>
>  ------------------------------
>
>
> ------------------------------------------------------------------------------
> Crystal Reports &#45; New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty&#45;free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
>
> ------------------------------
>
> _______________________________________________
> NAnt-users mailing list
> NAnt-users@...
> https://lists.sourceforge.net/lists/listinfo/nant-users
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports &#45; New Free Runtime and 30 Day Trial
> Check out the new simplified licensign option that enables unlimited
> royalty&#45;free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> NAnt-users mailing list
> NAnt-users@...
> https://lists.sourceforge.net/lists/listinfo/nant-users
>
>

Re: [NAnt-users] <call> task with parameters ...

[Bjerstedt, Tony [Audatex - Americas] <Tony.Bjerstedt@au...>]

I will try to put together a proposal in the next couple of days.

 

The following is subject to memory fade as I looked at it a few years
ago and started to explore a solution.

 

I had considered extending the property system to include a form of
scoping. Limiting visibility of a parameter or other locally scoped
property to only the task where it is defined would be extremely
difficult. I think I rejected this.

 

Possibly the simplest solution is something like the following:

1.     Call task starts.

2.     Save the values of parameters that already exist as properties
and note which parameters do not exist. (CALL context)

3.     Set/create property entries for the parameters listed under the
CALL

4.     Enter the designated target passing CALL context.

5.     The Parameter task checks if the name is present in the CALL
context. If missing and there is a default value, save any existing
value to the CALL context and set it to the default value.

6.     If property has "Local=yes", save previous value in LOCAL context
and set value.

7.     When target exits, any properties in local context are restored
to previous state (if local property did not exist, delete it). DO THIS
EVEN for an exception

8.     Return to Call.

9.     Restore properties in CALL context to original state (prior value
or remove if they didn't exist) DO THIS EVEN for an exception

10.  Every thing is back to normal.

 

 

From: Bob Archer [mailto:Bob.Archer@...] 
Sent: Wednesday, May 13, 2009 2:36 PM
To: Gert Driesen; Bjerstedt, Tony [Audatex - Americas]; 'Parrish, Ken';
nant-users@...
Subject: RE: [NAnt-users] <call> task with parameters ...

 

Would it be better to create a function or a task that you can pass
stuff to, rather than having to worry about property scoping?

 

BOb

 

 

________________________________

From: Gert Driesen [mailto:gert.driesen@...] 
Sent: Wednesday, May 13, 2009 3:04 PM
To: 'Bjerstedt, Tony [Audatex - Americas]'; 'Parrish, Ken';
nant-users@...
Subject: Re: [NAnt-users] <call> task with parameters ...

 

Hi Ken, Tony,

 

This is definitely something that I've considered as well.

Can one of you work out a proposal that can be discussed on the list?

 

Gert

 

From: Bjerstedt, Tony [Audatex - Americas]
[mailto:Tony.Bjerstedt@...] 
Sent: woensdag 13 mei 2009 20:01
To: Parrish, Ken; nant-users@...
Subject: Re: [NAnt-users] <call> task with parameters ...

 

I have wondered the same thing. If this were added, I would suggest an
approach similar to XSLT.

 

An XSLT like approach would look something like:

 

            <call target="name">

              <with-parameter name="param1" value="..."/>

              <with-parameter name="param2" value="..."/>

               ...

            </call>

 

and 

            <target name="name">

              <parameter name="param1" default="value"/>

              <parameter name="param2" />

              ...

            </target>           

 

A couple of years ago I started playing with this type of approach.

 

 

From: Parrish, Ken [mailto:KParrish@...] 
Sent: Wednesday, May 13, 2009 10:56 AM
To: nant-users@...
Subject: [NAnt-users] <call> task with parameters ...

 

Has there ever been any consideration to creating a mechanism for
executing the <call> task with a set of private, local parameters
(properties) which are only available inside the called task?

 

I'm not sure exactly how the syntax would work, but the idea would be to
pass, as an argument to the <call> task, a list of name/value pairs, or
a list of values that are identified by place or order.

 

I find the I often need to fabricate some sort of parameter passing
mechanism, using globally defined <properties> , to control <task>s that
are designed to be general purpose.  Typically, I'll create <property>
elements that have names which include the name of the task:

 

                <property name="mytask_sourceDir" value="sourceValue" />

                <call task="mytask" />

 

I'd much prefer something like:

 

                <call task="mytask" parameters="sourceDir=sourceValue"
/>

 

The assumption would be that the parameter 'sourceDir' is visible only
inside 'mytask'.

 

Thoughts, ideas, considerations?

 

Ken Parrish

Gomez, Inc.

 

 


-
------------------------------------------------------------------------
---



PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments)
is intended for the named recipient(s) only and may contain privileged
and confidential information. If you have received this message in
error, you are hereby notified that any use, disclosure, copying or
alteration of this message is strictly prohibited. If you are not the
intended recipient(s), please contact the sender by reply email and
destroy all copies of the original message. Thank you.



-
------------------------------------------------------------------------
--

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.5.285 / Virus Database: 270.12.2/2072 - Release Date:
04/21/09 16:48:00


- ---------------------------------------------------------------------------

 

PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments) is intended for the named recipient(s) only and may contain privileged and confidential information. If you have received this message in error, you are hereby notified that any use, disclosure, copying or alteration of this message is strictly prohibited.  If you are not the intended recipient(s), please contact the sender by reply email and destroy all copies of the original message.  Thank you.

 

- --------------------------------------------------------------------------

Re: [NAnt-users] script task

[Bob Archer <Bob.Archer@am...>]

Seems like I should just create a task in the script code and then call the task. Would be about the same amount of code, right? I just have to put the <task> after the script task.

I never created a task inline. But, since there is no way to sort a fileset I am finding I have to do some c# code here.

BOb


________________________________
From: Gert Driesen [mailto:gert.driesen@...]
Sent: Wednesday, May 13, 2009 3:44 PM
To: Bob Archer; nant-users@...
Subject: RE: [NAnt-users] script task

Hi Bob,

This is only done when logging from a task.
You could do something like this (although I agree it's a hack):

<project name="script-test" default="build">
    <target name="build">
        <script language="C#">
            <code>
                <![CDATA[
                    public static void ScriptMain (Project project)
                    {
                        Log (project, "ok");
                    }

                    private static void Log (Project project, string message)
                    {
                        Task task = new LogTask ();
                        task.Project = project;
                        task.Log (Level.Info, message);
                    }

                    [TaskName ("whatever")]
                    public class LogTask : Task
                    {
                        protected override void ExecuteTask ()
                        {
                        }
                    }
                ]]>
            </code>
        </script>
    </target>
</project>

Hope this helps,

Gert

From: Bob Archer [mailto:Bob.Archer@...]
Sent: woensdag 13 mei 2009 21:22
To: nant-users@...
Subject: [NAnt-users] script task

Ok,

I am trying to log from code in a script task. I use code such as this:

            project.Log(Level.Info, "I am in the script function.");

But the console log looks like this:

   [script] Scanning assembly "tommx7ja" for extensions.
I am in the script function.

What is it not formatted the same? Do I have to specify a certain logger or something?

BOb


Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.5.285 / Virus Database: 270.12.2/2072 - Release Date: 04/21/09 16:48:00

Re: [NAnt-users] script task

[Gert Driesen <gert.driesen@te...>]

Hi Bob,

 

This is only done when logging from a task.

You could do something like this (although I agree it's a hack):

 

<project name="script-test" default="build">

    <target name="build">

        <script language="C#">

            <code>

                <![CDATA[

                    public static void ScriptMain (Project project)

                    {

                        Log (project, "ok");

                    }

                        

                    private static void Log (Project project, string
message)

                    {

                        Task task = new LogTask ();

                        task.Project = project;

                        task.Log (Level.Info, message);

                    }

                              

                    [TaskName ("whatever")]

                    public class LogTask : Task

                    {

                        protected override void ExecuteTask ()

                        {

                        }

                    }

                ]]>

            </code>

        </script>

    </target>

</project>

 

Hope this helps,

 

Gert

 

From: Bob Archer [mailto:Bob.Archer@...] 
Sent: woensdag 13 mei 2009 21:22
To: nant-users@...
Subject: [NAnt-users] script task

 

Ok,

 

I am trying to log from code in a script task. I use code such as this:

 

            project.Log(Level.Info, "I am in the script function.");

 

But the console log looks like this:

 

   [script] Scanning assembly "tommx7ja" for extensions.

I am in the script function.

 

What is it not formatted the same? Do I have to specify a certain logger or
something?

 

BOb

 

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.5.285 / Virus Database: 270.12.2/2072 - Release Date: 04/21/09
16:48:00

Re: [NAnt-users] <call> task with parameters ...

[Bob Archer <Bob.Archer@am...>]

Would it be better to create a function or a task that you can pass stuff to, rather than having to worry about property scoping?

BOb


________________________________
From: Gert Driesen [mailto:gert.driesen@...]
Sent: Wednesday, May 13, 2009 3:04 PM
To: 'Bjerstedt, Tony [Audatex - Americas]'; 'Parrish, Ken'; nant-users@...
Subject: Re: [NAnt-users] <call> task with parameters ...

Hi Ken, Tony,

This is definitely something that I've considered as well.
Can one of you work out a proposal that can be discussed on the list?

Gert

From: Bjerstedt, Tony [Audatex - Americas] [mailto:Tony.Bjerstedt@...]
Sent: woensdag 13 mei 2009 20:01
To: Parrish, Ken; nant-users@...
Subject: Re: [NAnt-users] <call> task with parameters ...

I have wondered the same thing. If this were added, I would suggest an approach similar to XSLT.

An XSLT like approach would look something like:

            <call target="name">
              <with-parameter name="param1" value="..."/>
              <with-parameter name="param2" value="..."/>
               ...
            </call>

and
            <target name="name">
              <parameter name="param1" default="value"/>
              <parameter name="param2" />
              ...
            </target>

A couple of years ago I started playing with this type of approach.


From: Parrish, Ken [mailto:KParrish@...]
Sent: Wednesday, May 13, 2009 10:56 AM
To: nant-users@...
Subject: [NAnt-users] <call> task with parameters ...

Has there ever been any consideration to creating a mechanism for executing the <call> task with a set of private, local parameters (properties) which are only available inside the called task?

I'm not sure exactly how the syntax would work, but the idea would be to pass, as an argument to the <call> task, a list of name/value pairs, or a list of values that are identified by place or order.

I find the I often need to fabricate some sort of parameter passing mechanism, using globally defined <properties> , to control <task>s that are designed to be general purpose.  Typically, I'll create <property> elements that have names which include the name of the task:

                <property name="mytask_sourceDir" value="sourceValue" />
                <call task="mytask" />

I'd much prefer something like:

                <call task="mytask" parameters="sourceDir=sourceValue" />

The assumption would be that the parameter 'sourceDir' is visible only inside 'mytask'.

Thoughts, ideas, considerations?

Ken Parrish
Gomez, Inc.



- ---------------------------------------------------------------------------



PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments) is intended for the named recipient(s) only and may contain privileged and confidential information. If you have received this message in error, you are hereby notified that any use, disclosure, copying or alteration of this message is strictly prohibited. If you are not the intended recipient(s), please contact the sender by reply email and destroy all copies of the original message. Thank you.



- --------------------------------------------------------------------------

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.5.285 / Virus Database: 270.12.2/2072 - Release Date: 04/21/09 16:48:00

[NAnt-users] script task

[Bob Archer <Bob.Archer@am...>]

Ok,

I am trying to log from code in a script task. I use code such as this:

            project.Log(Level.Info, "I am in the script function.");

But the console log looks like this:

   [script] Scanning assembly "tommx7ja" for extensions.
I am in the script function.

What is it not formatted the same? Do I have to specify a certain logger or something?

BOb

Re: [NAnt-users] <call> task with parameters ...

[Gert Driesen <gert.driesen@te...>]

Hi Ken, Tony,

 

This is definitely something that I've considered as well.

Can one of you work out a proposal that can be discussed on the list?

 

Gert

 

From: Bjerstedt, Tony [Audatex - Americas]
[mailto:Tony.Bjerstedt@...] 
Sent: woensdag 13 mei 2009 20:01
To: Parrish, Ken; nant-users@...
Subject: Re: [NAnt-users] <call> task with parameters ...

 

I have wondered the same thing. If this were added, I would suggest an
approach similar to XSLT.

 

An XSLT like approach would look something like:

 

            <call target="name">

              <with-parameter name="param1" value="."/>

              <with-parameter name="param2" value="."/>

               .

            </call>

 

and 

            <target name="name">

              <parameter name="param1" default="value"/>

              <parameter name="param2" />

              .

            </target>           

 

A couple of years ago I started playing with this type of approach.

 

 

From: Parrish, Ken [mailto:KParrish@...] 
Sent: Wednesday, May 13, 2009 10:56 AM
To: nant-users@...
Subject: [NAnt-users] <call> task with parameters ...

 

Has there ever been any consideration to creating a mechanism for executing
the <call> task with a set of private, local parameters (properties) which
are only available inside the called task?

 

I'm not sure exactly how the syntax would work, but the idea would be to
pass, as an argument to the <call> task, a list of name/value pairs, or a
list of values that are identified by place or order.

 

I find the I often need to fabricate some sort of parameter passing
mechanism, using globally defined <properties> , to control <task>s that are
designed to be general purpose.  Typically, I'll create <property> elements
that have names which include the name of the task:

 

                <property name="mytask_sourceDir" value="sourceValue" />

                <call task="mytask" />

 

I'd much prefer something like:

 

                <call task="mytask" parameters="sourceDir=sourceValue" />

 

The assumption would be that the parameter 'sourceDir' is visible only
inside 'mytask'.

 

Thoughts, ideas, considerations?

 

Ken Parrish

Gomez, Inc.

 

 


-
---------------------------------------------------------------------------



PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments) is
intended for the named recipient(s) only and may contain privileged and
confidential information. If you have received this message in error, you
are hereby notified that any use, disclosure, copying or alteration of this
message is strictly prohibited. If you are not the intended recipient(s),
please contact the sender by reply email and destroy all copies of the
original message. Thank you.



- --------------------------------------------------------------------------

Internal Virus Database is out of date.
Checked by AVG - http://www.avg.com
Version: 8.5.285 / Virus Database: 270.12.2/2072 - Release Date: 04/21/09
16:48:00

Re: [NAnt-users] <call> task with parameters ...

[Bjerstedt, Tony [Audatex - Americas] <Tony.Bjerstedt@au...>]

I have wondered the same thing. If this were added, I would suggest an
approach similar to XSLT.

 

An XSLT like approach would look something like:

 

            <call target="name">

              <with-parameter name="param1" value="..."/>

              <with-parameter name="param2" value="..."/>

               ...

            </call>

 

and 

            <target name="name">

              <parameter name="param1" default="value"/>

              <parameter name="param2" />

              ...

            </target>           

 

A couple of years ago I started playing with this type of approach.

 

 

From: Parrish, Ken [mailto:KParrish@...] 
Sent: Wednesday, May 13, 2009 10:56 AM
To: nant-users@...
Subject: [NAnt-users] <call> task with parameters ...

 

Has there ever been any consideration to creating a mechanism for
executing the <call> task with a set of private, local parameters
(properties) which are only available inside the called task?

 

I'm not sure exactly how the syntax would work, but the idea would be to
pass, as an argument to the <call> task, a list of name/value pairs, or
a list of values that are identified by place or order.

 

I find the I often need to fabricate some sort of parameter passing
mechanism, using globally defined <properties> , to control <task>s that
are designed to be general purpose.  Typically, I'll create <property>
elements that have names which include the name of the task:

 

                <property name="mytask_sourceDir" value="sourceValue" />

                <call task="mytask" />

 

I'd much prefer something like:

 

                <call task="mytask" parameters="sourceDir=sourceValue"
/>

 

The assumption would be that the parameter 'sourceDir' is visible only
inside 'mytask'.

 

Thoughts, ideas, considerations?

 

Ken Parrish

Gomez, Inc.

 

 


- ---------------------------------------------------------------------------

 

PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments) is intended for the named recipient(s) only and may contain privileged and confidential information. If you have received this message in error, you are hereby notified that any use, disclosure, copying or alteration of this message is strictly prohibited.  If you are not the intended recipient(s), please contact the sender by reply email and destroy all copies of the original message.  Thank you.

 

- --------------------------------------------------------------------------

[NAnt-users] <call> task with parameters ...

[Parrish, Ken <KParrish@go...>]

Has there ever been any consideration to creating a mechanism for executing the <call> task with a set of private, local parameters (properties) which are only available inside the called task?

I'm not sure exactly how the syntax would work, but the idea would be to pass, as an argument to the <call> task, a list of name/value pairs, or a list of values that are identified by place or order.

I find the I often need to fabricate some sort of parameter passing mechanism, using globally defined <properties> , to control <task>s that are designed to be general purpose.  Typically, I'll create <property> elements that have names which include the name of the task:

                <property name="mytask_sourceDir" value="sourceValue" />
                <call task="mytask" />

I'd much prefer something like:

                <call task="mytask" parameters="sourceDir=sourceValue" />

The assumption would be that the parameter 'sourceDir' is visible only inside 'mytask'.

Thoughts, ideas, considerations?

Ken Parrish
Gomez, Inc.

[NAnt-users] Reliability of NAnt vssget task in getting labeled files

[Munawar Rashid <a_m_rashid@ho...>]

I've posted this issue in NAnt forum too. I just thought imight be worthwhile to thread it over here too. 
Has anybody faced any issue with the subject of this post. 
I have already been using the combo of NAnt 'vsslabel' and 'vssget' task with the 'version' attribute, to pull labeled codes and its seemingly working fine.
I've even done some spot-check to make sure its bringing down the files correctly. 
But my manager recently raised a concern that previously he has seen issues in the application that was attributed to 'vssget' malfunctioning while pulling down labeled code. 
He's asked me to explore writing a script to check whether files are being brought down correctly and incorporate into the build. 
My concern is that it will probably increase build time. 
So I want to know if a script like this just to check whether an NAnt task is working the way its supposed to, really necessary.

[NAnt-users] Re liability of NAnt vssget task in getting labeled files

[shampoo72 <a_m_rashid@ho...>]

Has anybody faced any issue with the subject of this post. 
I have already been using the combo of NAnt 'vsslabel' and 'vssget' task
with the 'version' attribute, to pull labeled codes and its seemingly
working fine.
I've even done some spot-check to make sure its bringing down the files
correctly. 
But my manager recently raised a concern that previously he has seen issues
in the application that was attributed to 'vssget' malfunctioning while
pulling down labeled code. 
He's asked me to explore writing a script to check whether files are being
brought down correctly and incorporate into the build. 
My concern is that it will probably increase build time. 
So I want to know if a script like this just to check whether an NAnt task
is working the way its supposed to, really necessary.
-- 
View this message in context: http://www.nabble.com/Reliability-of-NAnt-vssget-task-in-getting-labeled-files-tp23464057p23464057.html
Sent from the NAnt - Users mailing list archive at Nabble.com.

[NAnt-users] Sort a fileset...

[Bob Archer <Bob.Archer@am...>]

Is there a way to sort a fileset?

What I want to do is delete all of the folders in a location except for the newest 5. I thought if I could sort the fileset by file date then in a foreach I can just skip the first 5 folders in the set.

Or, is there another, easier way to do this?

BOb