Note that I think the wix announcement is cool just for the fact of
microsoft releasing somthing on sourceforge. If there is widespread
uptake migrating the msi tasks to the wiks format might be the right move.
Ian
Ian MacLean wrote:
Heres a response from Jayme Edwards - the original author of
Heres a response from Jayme Edwards - the original author of NAnts msi
tasks - which actually perform in a similar manner to wix. ( posed as a
reply to the original announcement )
Wow,
Well here we go again. As the original contributor of the MSI task to
NAnt's "NAntContrib" project (http://n
How exciting would an NAnt Wix task or refactoring of the NAntContrib - Msi/Msm tasks be! Maybe I'll work on a transform for vdproj -> Wix xml.
http://blogs.msdn.com/robmen/archive/2004/04/05/107709.aspx
http://sourceforge.net/projects/wix Tax headache? MSN Money provides relief with tax tips, t
Noel,
This
bugged me as well till I took it one step at a time. IIS6 is totally
different from IIS5 or IIS5.1, so there are a bunch of properties that are
trying to be set that fail.
If
you remove the following properties from the MkIISDir and IISDirInfo task, it
will work fine.
A
- Original Message -
From: "Michael Dang" <[EMAIL PROTECTED]>
To: "Gert Driesen" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Monday, April 05, 2004 7:51 PM
Subject: Re: [Nant-users] CSC Output Build Internal Error help
>
> Wonder if there is a better way to identify the namespace and
Gert,
I'd like a parameter added to the delete task (or maybe the fileset task)
specifying whether directories should be deleted.
When I used the task I expected only the files to be removed.
Bob,
The script below in target "use_foreach" will delete all files below
${DelDir} and leave the di
Gert,
I found the problem. In the Nant.Dotnet project,
PerformSearchForResourceLinkage method.
You read the .cs file and look for the first occurance of the
keywords "namespace" and "class". "class" was the problem in my
case.
matchClassName.Groups["class"];
It seems that one of the developers
Jo,
You don't need to nest the ${} syntax. Everything inside a ${} block is
an expression so you can reference properties by name. So what you need is:
${string::replace( testReplace,'bb', testValue) }
hope that helps.
Ian
Jo De Greef wrote:
Hi all,
I try to do a string::replace on one of my
Ok,
What the trick to deleting all files from directory and
still leaving the directory intact.
I have obviously tried everything except for the correct
thing…
I basically want the equivalent of:
Del c:\directory\*.*
/s
So, directory still exists after the delete. This i
- Original Message -
From: "Jo De Greef" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, April 05, 2004 4:52 PM
Subject: [Nant-users] String::replace problem
> Hi all,
>
> I try to do a string::replace on one of my properties as following:
>
>
>
>
> message="${string::re
Hi all,
I try to do a string::replace on one of my properties as following:
I would expect to get 'aazzcc' but instead this is the result:
[echo] ${testReplace}
[echo] aabbcc
It looks like Nant doesn't parse the parameters correctly: it treats
'${t
Yes, it's included in the nightly builds (since December 2003) and will be
included in future stable releases. It has been greatly enhanced since the
nant-ee-test1.zip release. See http://nant.sf.net/ for more information.
Documentation can be found at:
http://nant.sourceforge.net/nightly/help/fu
In my opinion, the 0.85 nightly builds are far more stable than the 0.84
release.
I'm not saying that we might not rename some tasks or functions, but there
are definitely less bugs in the nightly builds.
Gert
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMA
Great, Thanks Gert.
At the risk of seeming overly cautious, could I ask how stable the nightly
builds are? Am I safe to use them as the basis of building our software?
If not, then what is the likely release date for 0.85?
Many thanks,
Bill
-Original Message-
From: Gert Driesen [
Bill,
This was actually a bug in the nant task. The properties you specified as
nested elements, were evaluated in the context of the new project. I
changed this to evaluate the properties in the current build file, when the
property is not dynamic.
This fix has been committed to cvs and will b
Do you need to set readonly="true" on the properties you are passing in?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> Sent: 05 April 2004 07:58
> To: [EMAIL PROTECTED]
> Subject: [Nant-users] Properties problem on task
>
>
> Hi,
>
> I have a bit of a p
Hi,
I have a bit of a problem with the task and can't see what's wrong.
Below is a copy of my build script and the associated output. According to
the documentation, I should be able to use a property value in my current
project to pass through top a new NAnt instance, but it seems to be failing
17 matches
Mail list logo
