Thanks Bob!
That fixed it.
-Original Message-
From: Bob Archer [mailto:bob.arc...@amsi.com]
Sent: Monday, June 17, 2013 1:18 PM
To: Labout, Douglas; 'nant-users@lists.sourceforge.net'
Subject: RE: Nested variables
Right... so use the property::get-value() function. I think this is what yo
Right... so use the property::get-value() function. I think this is what you
need to do:
${ProjectName} ${V
Hmm,
Let's see if I can explain it better...
Here is the properties file that contains all the components to be built and
their associated views and labels.
# Projects Build Order
Project.Name=WCFServices
Project.Build.Directory=C:\/VisualStudio\/
Project.Build.Order=NETComponents,NETDLLs,App
Pr
Ok... I guess I'm still not understanding what is in each variable:
> You are correct in that I'm trying to put together a couple of variables.
> The build order is assigned to the variable ${properties.project.Ord}. I then
What is the exact text in that variable?
> append to the end of that var
Bob,
You are correct in that I'm trying to put together a couple of variables.
The build order is assigned to the variable ${properties.project.Ord}. I then
append to the end of that variable the .ProjectName, .ViewName, and .Label and
assign them to ${ProjectName}. I then pass $ProjectName to my
> Hello,
> I'm working on converting an Ant script to Nant and have ran into an issue
> with
> joining several variables together in Nant.
>
> Below is the original Ant script in which it pulls information from a
> properties
> file and uses the information to feed the build. The project starts
> Hello,
> I'm working on converting an Ant script to Nant and have ran into an issue
> with
> joining several variables together in Nant.
>
> Below is the original Ant script in which it pulls information from a
> properties
> file and uses the information to feed the build. The project starts
