You'd probably want to call it then.
Damir
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian
MacLean
Sent: Monday, December 15, 2003 4:06 AM
To: Jaroslaw Kowalski
Cc: Nant-Developers (E-Mail); William E Caputo
Subject: Re: [nant-dev] SUBMISSION: Path
I have 4 files: one
in the root folder, three in a subfolder.
In the root folder
there is the main build file which includes one of the files in the subfolder.
This other file includes another two. Thus:
Main file has
inc/included.build
has:
According to an
email I found (http
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Damir
Simunic
Sent: 29. studeni 2003 20:59
To: [EMAIL PROTECTED]
Subject: [nant-dev] task behavior and nant.onfailure
...
In addition, in all three scenarios any message after the task
is never printed
I've found some issues in handling forced failures in NAnt v0.8.4.31128.
What happens is that I have a nant.onfailure task set. Somewhere in the
build script, I'm failing the build with
task. The onfailure handler calls a cleanup target that happens to have an
error.
If the call to the cleanup
I've noticed that
nightly builds come with version number out of sync: just downloaded
0.8.4.31128, but properties of NAnt.exe show 0.8.4.31114.
Running nant -help
shows 0.8.4.0.
As a small
convenience, do you think it would be possible to package the build in a
version-numbered folde
MSBuild is obviously a child of Embrace & Extend philosophy; being built-in
in the next version of the framework will do wonders in terms of promoting
the process of automated builds, which are critical to quality in our line
of work. That is a good thing. Nant is already doing it. And that is even
Since there is so much interest in this msbuild thing, here's the list of
namespaces Microsoft.Build.BuildEngine
When you open the link, click on 'sync toc' to see the rest of
Microsoft.Build.* namespaces in the TOC.
http://longhorn.msdn.microsoft.com/?//longhorn.msdn.microsoft.com/lhsdk/ref/
mic
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,
