Rod Ayers wrote:
Hi, all
I'm trying to get a clear understanding of the impact of using
.
1. The contents of the included file makes the included code act as
if it was all part of one build file.
2. Tasks in the included file would be invoked with , rather
than as with "separate"
Rod Ayers wrote:
The other situation is where I don't have a complete environment available, or
I'm trying to assess task flow. Both of these conditions are presently true
right now as I'm starting up a BizTalk Build/Deploy autoamtion project. Yes, I
have found lots of sample code. Now I w
Title: Using Include
Hi, all
I'm trying to get a clear understanding of the impact of using .
1. The contents of the included file makes the included code act as if it was all part of one build file.
2. Tasks in the included file would be invoked with , rather than as with "sep
Hi, Gary
Yes, I have used the "driver"/"worker" task pair in different contexts. E.g,
I've split a task to simplify what otherwise might be a rather convoluted "If".
There are a couple of situations I want to avoid. The easier one is to be able
to just look at the flow, and not "parse out
Title: Re: [NAnt-users] Traversing Directories
Thanks that did it!
From: Noel Gifford
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 28, 2006
10:06 PM
To: Bryan D. Andrews; 'Rod Ayers';
nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] Getting
full path
Try t
