But the issue here is if I have created a folder named obj
(different
from the intermediate obj folder) which contains some files that I
use
in the project, then this clean target will also delete my obj
folder which I do not want to happen. Could you guide in this case?
My immediate thought
that ${file:exists(${solution.file})} would throw an
extraneous propertly nesting error/exception instead of returning
false, no file found.
Just a thought ...
Bevan.
Bevan Arps
Senior Analyst/Programmer | Knowledge Services Group | Reserve Bank
of New Zealand
( +64 (0)4 471 3689 | * [EMAIL
Hi Eric.
I don't see much use for NAnt except for legacy stuff.
For what it's worth, I see a place for both tools.
In a significant project I'm working on at the moment, we use MSBuild to
do the actual builds ... But we control it by invoking it from within
NAnt.
Our NAnt scripts take care
My 2c worth ...
The current version of NAnt is more than worthy of 1.0 status - it's
functional, stable and mature.
So I'm fully behind the idea of tagging the current 0.85rc4 as 0.85
final and then working quickly towards 1.00 in the very near future.
Keep Smiling,
Bevan.
-Original
Thought I'd throw in my 2c as a heavy NAnt user.
Gert wrote:
Do you think we should support VS.NET 2005 solutions/projects in
the solution task ?
My thought is that the solution task should *only* handle Visual
Studio 2003 projects.
Why?
It seems to me that VS2003 and VS2005 are
Hi Adrian.
When I attempt to perform a build operation on my
folder I get this error. In response to the request
in the error, I am sending this to you.
Well, you've provided next to no information that we here on the list
can use to diagnose your problem, so it's kinda difficult to help.
