Mitch,
If anything, I would think that the xpath expression language would be a
good start. I'm not sure if I would want an expression language included
with nant though. This could however be an addin, or extension. Adding
expressions (as we have discussed before) seems to me to be just one more
make bootstrap
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-bootstrap;
else make linux-bootstrap; fi
make[2]: Entering directory `/root/nant'
cp lib/*.* bin/
cp lib/mono/1.0/*.* bin/
make linux-bootstrap-nant
make[3]: Entering directory `/root/nant'
mcs -targe
Hi folks,
I'm wondering if anyone has looked into building expression support into
NAnt. For example, it would be cool to be able to do this:
I've been doing some digging and it looks like the path of least
resistance for implementing something like this would be around the
ExpandProper
asmodeus nant # make
make bootstrap
make[1]: Entering directory `/root/nant'
if test x = xWindows_NT; then make windows-bootstrap;
else make linux-bootstrap; fi
make[2]: Entering directory `/root/nant'
cp lib/*.* bin/
cp lib/mono/1.0/*.* bin/
make linux-bootstrap-nant
make[3]: Entering directory `/
Ian,
I've tried out the new csc task -- it definitely works for .resx files, but
any other type of resource will still be embedded in the main assembly.
For example, if the project has text files, such as 'strings.fr-FR.txt' and
'strings.de-CH.txt', those will be included in the main assembly,
Hello,
unfortunately, I've lost the track of the current development of nant
and now I just can't catch up (I haven't had the e-mail in september,
thus I've missed lots of things which were going on since the 0.8.3).
I'm using nant-0.8.3 and waiting for the next stable version to join
the developm
