I had the same problem. It is in RC4, but not in
RC3. I downloaded RC4 yesterday so it is definately
available.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve
WhitleySent: Fri 28 July 2006 07:41To:
nant-users@lists.sourceforge.netSubject: Re: [NAnt-use
I might be missing something, but I couldn't get on as it insists you know the
wiki password. I only wanted to read the site, but couldn't see any
alternative links for bypassing the logon.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Ian MacLean
Sent:
Arrggghhh! What is wrong with some people. I went to the NAntUsage page for
some help, and it's trying to sell me drugs and cheap airline tickets!! I
wonder if it's possible to lock wiki's based on IP address of editor?
Visit our website at http://www.ubs.com
This message contains confid
Can anyone point me at any resources for writing my own NAnt tasks (other than
the reference oriented SDK). I nice into/explanation/tutorial would be very
helpful to get started.
Thx
Mark
Visit our website at http://www.ubs.com
This message contains confidential information and is intended o
My
choice has been not to use PostBuild steps wherever possible. I don't like
them as they are opaque to the build process, especially when run within
NAnt. I always write targets in any NAnt build scripts to handle this sort
of post build processing. Reasons are:
- it's a lot easie
> I wasn't sure where else to send this...
>
> Unfortunately, the NAnt Wiki has been hijacked by spammers. All links from
> the front page lead to absolute rubbish. Hope someone can fix it.
>
> Mark
Visit our website at http://www.ubs.com
This message contains confidential information and
Colin
I cannot get it to load a build script.
I chose not to install NAnt during the installation because I already have NAnt
installed. It now cannot find NAnt.Core. It only looks under the apps
installation path for NAnt dlls. I tried setting the NAntPath key in the
app.config, but that
In my view, some reasons are:
1. It brings together the control of flow and extra build/packaging steps into
one technology, rather than having to write dos batch scripts (shiver) to hook
together many different tools.
2. By addmission of an MS consultant, Microsoft have never, and never will u
