Hello,
I have been using the 0.85 nightly builds with great success. The
builtin functions have proven invaluable.
Do you have a ballpark date for the next official release (i.e., 0.86)?
My organization will not depend on unofficial releases of NAnt.
Lastly, NAnt is a fantastic product. Thank
Change
your to reference the DLL in the binDebug directory
Noel
-Original
Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Brian B
Using
also works
-Original
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Brian Beaudet
Sent: Tuesday, April 06, 2004
12:54 PM
You should reference bin\Debug\lib.dll instead of lib.dll
Hope it helps.
Jarek
- Original Message -
From: "Brian Beaudet" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 06, 2004 10:54 PM
Subject: [Nant-users] Newbie Question Regarding Referencing Assemblies
> I've go
I’ve got two simple *.cs files:
One called app.cs as shown below:
using System;
public class App
{
public static void Main()
{
Console.WriteLine( "1 +
1 = {0}", Calculator.Add( 1, 1 ) );
}
}
and another called lib.cs as shown below:
I believe it depends on how you select the files into the zip. I could run a
test, but I think this will make sense.
[please excuse my xml shorthand]
vs.
This is actually true a lot of places where filesets are used in tasks.
- Original Message -
From: "Andrew Sharpe" <
Forgive my ignorance, but is there any way with the
zip task to get it to ignore the path information? If
I zip up files in c:\temp directory, it will append
the temp directory to all the zipped files, and
therefore when I unzip them it will create the temp
directory. In Winzip the setting is cal
> - Original Message -
> From: "James Geurts" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
> Sent: Tuesday, April 06, 2004 3:27 PM
> Subject: Re: FW: [Nant-users] Wix!!!
>
> Sorry for my initial post of "disgust" related to Wix. It is sort of h
Hi Bob,
It might be worth taking a look at this page. A while ago, I conglomerated
some ideas into two tasks. They grab and increment the version number in an
AssemblyInfo.cs file. I find it useful when dealing with source control and
when not able to generate the assemblyInfo...
http://blogs.
Yep, I would like to have the conversion working with the solution task at
some point. Right now, the msi/msm tasks do not support how VS.Net adds
dialogs to the msi database (configurable merge modules), so that needs to
be taken into account. Unfortunately WiX doesn't support them either... So,
Title: Message
DUH? The asminfo task… how did I
miss that.
Thanks folks!
Bob
From: Clayton Harbour
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 06, 2004
11:20 AM
To: Bob
Archer; [EMAIL PROTECTED]
Subject: RE: [Nant-users]
Versioning the Assembly
Hi Bob,
Title: Message
Hi
Bob,
You
want to look at the task located here:
http://nant.sourceforge.net/help/tasks/asminfo.html
For
examples you can check out NAnt's build file here:
http://cvs.sourceforge.net/viewcvs.py/nant/nant/NAnt.build?annotate=1.151
line: 74
Cheers,
Clay
Title: Message
While
I have not done this yet, I plan on it. Try using the task
to create an AssemblyInfo file on the fly. Then, check in the newly create
file.
Hope
that helps,
Evan A. Bonnett
Reynolds and Reynolds,
IT
-Original Message-From:
Bob Archer [mailto:[EMAIL
Title: Message
I have
written Nant CustomTask to update the Assembly version
automatically.
We
have a process for automated build, which uses this task and increments the
assembly version for the project.
The
assembly version can be incremented for Major, Minor, incremental
builds.
My
b
Ok,
Here’s the kicker. I am using the Version task to
create my build number. Now, how do I update the version numbers of the
assemblies to match? I assume checking out the AssemblyInfo.cs files which I
can do, updating them (not so sure about) and checking them back in.
If anyone c
It would seem to me that if a solid transform could be created to go from vdproj to wixml (ooh ooh - new word!) there would be no reason the solution task couldn't use that or depend on a new wix task(s).
Original Message Follows
From: Ian MacLean <[EMAIL PROTECTED]>
To: James Geurts <[E
Hello all,
Does anyone know of a ballpark date for an "official" release of 0.85
(i.e., 0.86)?
I have found the built-in functions to be invaluable for complex build
scripts. Unfortunately, my organization will not depend on
"unofficial" releases of NAnt.
Finally, I would like to thank the NAnt
This looks interesting. Would we be able to hook it to the solution task
to just build vdproj projects or is some manual editing required post
conversion ?
Ian
In the mean time, I’ll also switch gears with my vdproj converter project
and look at generating the necessary xml fragment to be consu
Sorry for my initial post of "disgust" related to Wix. It is sort of hard
watching the baby that I helped nurture for the past two years just get
punted by Microsoft.
I agree that it will probably be a better thing for everyone, if we do
migrate away from supporting the msi/msm tasks and eventual
I completely agree - msi2xml and nant msi tasks are all more than sufficient, but i'm excited to see this unprecedented move towards community collaboration.
Original Message Follows
From: Ian MacLean <[EMAIL PROTECTED]>
To: Ian MacLean <[EMAIL PROTECTED]>
CC: Ryan Cromwell <[EMAIL PROT
20 matches
Mail list logo
