I was seeing this error yesterday when the vbc task was executing from c:\
If I changed paths to any sub directory it went away. Or if I set project
basedir=some dir ... it also went away.
It has been on my list of things to do to track down this bug.
Kevin Miller
-Original Message-
Hi:
I'm developing the install task for the comunit project (http:\\comunit.sf.net) and
found that with the latest CVS the .build is failing with the following error.
--
Buildfile: file:///D:/nant/Comunit/comunit/comunit.build
[tstamp] Martes, 10 de Septiembre de 2002 12:59:24
Title: RE: [nant-dev] patch to support resolving properties from environment vars
This would be great and would allow for individual customizations per a developers environment.
-Original Message-
From: Ben Lowery [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 10, 2002 3:27
Title: Message
Not being very NAnt/Ant knowledgeable yet
(and coming from a GNU make background), does such a task exist? I agree, it
would be nice to be able to differentiate and be explicit about where values
are coming from.
Cort
-Original Message-
From: Smith, Eric V.
Oh yeah, you could also just import the environment variables using the
sysinfo [1] task if you do want to use environment variables - which I
don't think is a good idea if you expect your builds to work right out
of the box.
[1] http://nant.sourceforge.net/help/tasks/sysinfotask.html
What do people think of this addition to the format of filesets? Look at
the sources element of the build task. The build task is my own
private task. I thought it would be better to include the entire buildfile
in full so that if people could come up with a better syntax they could edit
the
yay, i started conversation on this! perfect... code first / ask questions
later appears to be the way to go. :)
alright, so some commentary on the options presented and why i chose to go
for env vars. this is going to be long, consider this a warning. :)
first, the options using xml config
