Hi Mitch,
The xmlpeek and poke tasks could be very useful for a build issue we are
having currently. Out .config files default to haveing a
defaultframework attribute of net-1.0. However on a 1.1 only platform
we need to take a copy and change that attribute to net-1.1 or whatever
the current
Hi folks,
Its funny someone should raise this now. I've started writing a bunch of
tasks to do things like dependency and build output management. So far I
have three tasks with another three to come to close the loop.
Title: Message
How do I unsubscribe from the
mailing list.
Thanks for you
help
Skarthik
-Original Message-From: Anthony LoveFrancisco
[mailto:[EMAIL PROTECTED]Sent: Tuesday, September 16, 2003 2:13
PMTo: Jaroslaw Kowalski; Daniel Nguyen;
[EMAIL PROTECTED];
[EMAIL PROTE
Anthony LoveFrancisco asked when to write a task, versus make an exec call
versus when to use nant scripting. Here's my thoughts:
Tasks serve at least four functions the other two don't:
1) Portability. (as Anthony mentioned) in some cases abstracting the
implementation makes something more plat
Title: Message
It's just an edge condition
that needs to be checked.
At one point there was
discussion of using the ymmdd as part of the build number for NAnt.
Later I proposed just using number of days since a particular date and just
incrementing that.
-
Ants
-Original Messa
Jaroslaw,
Cool! Thanks so much for
your help. This is exactly what I was looking for. :-)
Daniel
-Original Message-From: Jaroslaw Kowalski
[mailto:[EMAIL PROTECTED]Sent: Tuesday, September 16, 2003 12:33
PMTo: Daniel Nguyen; [EMAIL PROTECTED];
[EMAIL PROTECTED]Subject:
Title: Message
Yes, but who would want build numbers to be
that high?
Jarek
- Original Message -
From:
Anthony LoveFrancisco
To: 'Jaroslaw Kowalski' ; 'Daniel Nguyen' ; [EMAIL PROTECTED]
; [EMAIL PROTECTED]
Sent: Tuesday, September 16, 2003 8:15
PM
Subject:
Title: Message
Oops, sorry, my bad. I think
that 65535 is the upper limit for build number parts which less than
Int32.Max.
-
Ants
-Original Message-From: Jaroslaw
Kowalski [mailto:[EMAIL PROTECTED] Sent: Tuesday, 16 September, 2003
11:05To: Anthony LoveFrancisco; 'Danie
Title: Message
Because you can either provide a
platform-independend executable and nant will run it or compile it
on-the-fly using task. So you need nothing but NAnt + your
project. The source code for both utilities is trivial as opposed to "sed"
or "awk" sourcecode which requires a rathe
Title: Message
Before I ruffle too many
feathers, I asked my question in the previous message for my own edification.
I'm trying to grok the NAnt philosophy.
[I'm seeing a lot of grey area
between where something must be written as a task, versus , versus
just write a
Title: Message
But does your AssemblyInfo.cs
file compile with a value greater than 255 in one of the build number
parts?
-
Ants
-Original Message-From: Jaroslaw
Kowalski [mailto:[EMAIL PROTECTED] Sent: Tuesday, 16 September, 2003
10:56To: Anthony LoveFrancisco; 'Daniel
Title: Message
Yes, it seems to be legal: a snapshot of my
ILDASM dump:
.assembly extern Sooda{
.publickeytoken = (36 D3 1D A5 0D 00 DE DD
)
// 6... .ver 1234:1234:1234:5}
Jarek
- Original Message -
From:
Anthony LoveFrancisco
To: '
Title: Message
I like this suggestion. It's
very clean and streamline.
I do have a general question to
though: I shot down for suggesting using awk or sed to update the
AssemblyInfo.cs because it uses an executable outside of the NAnt framework. Why
is this any different?
-
Ants
-
Title: Message
No problem: I use strings, not characters,
then Int32.Parse() them.
I've just checked on "0.0.0.5" and it
works.
Jarek
- Original Message -
From:
Anthony LoveFrancisco
To: 'Jaroslaw Kowalski' ; 'Daniel Nguyen' ; [EMAIL PROTECTED]
; [EMAIL PROTECTE
Title: Message
In ReplaceVersion.cs, I wonder
if DirectoryInfo.GetFiles(string) to see if the AssemblyInfo.cs file
exists.
-
Ants
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jaroslaw
KowalskiSent: Tuesday, 16 September, 2003 10:33T
Title: Message
In NewBuild.cs, how do you keep
each part of the build number from overflowing the upper limit
of 255?
-
Ants
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jaroslaw
KowalskiSent: Tuesday, 16 September, 2003 10:33To:
You can use my trick:
The technique consists of:
1. A plain text file that holds nothing but a version number
AA.BB.CC.DD (version.txt)
2. A small C# utility that increments one of the components in
the file (NewBuild.exe)
3. A small C# utility that replaces AssemblyVersion(...)
in all As
Greeting,
My apologies in advance if the
following questions have been asked before. But, does anyone know how
to increase the AssemblyVersion build number everytime it builds? Does
NAnt has any task to take care of this?
Example:
[assembly: AssemblyVersion("2003.1.0.0")]
The number I w
hi,
you can probably try the following :
- move this source code line from your AssemblyInfo file to a new file (eg KeyInfo.cs)
[assembly: AssemblyKeyFile(@"..\..\developers.key")]
- whenever you build with NAnt, use the asminfo task to generate this file,
overwriting the old value with what
I have exactly the same problem as you, and it seems not to have been corrected since
then.
I took care of setting the "Copy Local" property of my file reference to "False", but
the
solution task still copies 43 files in my output directory.
There is actually a slight difference of behavi
You're right Jean. In fact I was thinking much the same thing after I
posted. -projecthelp should just be informational.
Ian
Ian,
if there were no side-effects to initializing the build file(s), i'd say
"why not", but it seems it's a little more complex than that -- you'd
want to process and b
it would require that the csc call in the solution task introduce an
extra DEFINE. this could be useful at large. i don't know if it's
there already...
meanwhile, you could create a new solution configuration (eg:
nantdebug), place the DEFINE in there, and reference it in the
just thinkin...
Ian,
if there were no side-effects to initializing the build file(s), i'd say
"why not", but it seems it's a little more complex than that -- you'd
want to process and but no other project-level
task, then show the target list. so, is it worth your while? also,
wouldn't we still want an xslt
It would be great to be able to set additional defines for the compiler when
you build with the task.
We could for example need a define that sets the AssemblyKeyFile attribute
correct if we build with VS.NET or NANT
#ifdef NANT
[assembly: AssemblyKeyFile(@"..\NAnt.key")]
#else
[assembly: Assembly
24 matches
Mail list logo
