I don't use the solution task, but I'm guessing that the problem is that you
are missing the following at the top of your solution file:
- Ants
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED] On Behalf Of
| Kent Boogaart
| Sent: Wednesday, 01 October, 2003
ginal Message-From: Jaroslaw
Kowalski [mailto:[EMAIL PROTECTED] Sent: Tuesday, 16 September, 2003
11:52To: Anthony LoveFrancisco; 'Daniel Nguyen';
[EMAIL PROTECTED];
[EMAIL PROTECTED]Subject: Re: [nant-dev] RE:
[Nant-users] How do one update the AssemblyVersion build
num
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
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; 'D
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
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:
Overall, I like the idea, but I'm wondering the utility/value of a set of
new tasks versus just invoking sed/awk/perl from an exec task ?
- Ants
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED] On Behalf Of
| Jaroslaw Kowalski
| Sent: Tuesday, 19 August, 2
Does the csc task support having two "references" nodes one of which has
basedir defined as Jesper Rassmusen is using below ?
- Ants
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED] On Behalf Of
| Erv Walter
| Sent: Thursday, 07 August, 2003 07:54
| To: J
Are use using tlbimp via the exec task, or the tlbimp task. If the latter,
then I think it would be better if you fixed the tlbimp task (and send us
the patch), rather than putting another workaround.
The beauty of Nant is the minimal set of configuration that needs to be done
out of the box. (I'm
Title: Message
Does your project specify a
basedir and what is it set to ?
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Reggie
BurnettSent: Friday, 20 June, 2003 09:50To:
[EMAIL PROTECTED]Subject: [Nant-users] mono 0.24
failure
You can do this using the
Title: Message
I think you can
use:
:
:
-
Ants
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
brian.nantzSent: Monday, 09 June, 2003 06:08To:
[EMAIL PROTECTED]Subject: [Nant-users] CSC task
Title: Message
The cl task always uses the -c
option which compiles an object file into the "outputdir" specified. It doesn't
do the link step for you.
- Ants "Still
working on the dependency checking for cl"
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTE
15 matches
Mail list logo
