audience then
they could cherry pick from the NAntContrib and include it in a future
release.
I don't see the need to include ALL tasks into NAnt (but I do think that
most of the tasks submitted are generally usefull), and that tasks not
included should stay in NAntContrib.
brant
...
- Original
yet.
I will be working on a patch for these soon.
brant
...
- Original Message -
From: Tom Cabanski [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 2:47 PM
Subject: [nant-dev] Contributing
I've cleaned up a variety of little bugs in the solution task as follows
Was there ever any decision on this? IMO allowing multiple includes makes
managing multiple build files much easier.
brant
...
- Original Message -
From: Gert Driesen [EMAIL PROTECTED]
To: Brant Carter [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Friday, August 15, 2003 1:40 AM
Subject
This task already exists, but in a limited form (the IISTask). It would be
a good starting point.
brant
...
- Original Message -
From: John Lam [EMAIL PROTECTED]
To: NAnt developers (E-mail) [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 9:32 PM
Subject: RE: [nant-dev] NAnt
Please consider refactoring the existing project class into separate classes
ie: BaseProject, CSharpProject, VBNetProject and CPlusPlusProject
this will help keep the subtle details of each project file separate. This
was on my list of contributions but I haven't had time to start on it yet.
Is there any reason why we don't just use the existing Wiki as the Default
Home page; and build up the content from that? If the existing Wiki isn't
great (which I don't think it is); we could move to a nicer / fancier one
like MediaWiki. I have used OpenWiki as well which is very nice and
} debug=${debug}
define=${define} doc=${doc} rootnamespace=App1 .../
arg value=/m:App1.Form1 /
Adding the arg tag with the /m option.
brant
...
_
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*
http
values in a
nant.exe.config file (or possibly the nunit.exe.config file). I haven't
confirmed this yet as I haven't ventured into NUnit/NAnt integration just
yet.
brant
...
- Original Message -
From: Scott Hernandez [EMAIL PROTECTED]
To: Sansone, Aaron [EMAIL PROTECTED];
[EMAIL PROTECTED
+1 for this. This would be really sweet.
brant
...
From: Philip Nelson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [nant-dev] Fileset references
Date: Thu, 20 Mar 2003 11:15:20 -0800 (PST)
So the two valid forms would be:
1.) (how things work now)
foreach ...
!-- stuff to do
. It
uses the location of the GAC and if its not set you get a Null Reference
Exception.
brant
...
_
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
Where can I get the NAntContrib source that is being use for the 0.83
release. I downloaded the source for NAnt and the binaries are in the \bin
folder. The nightly builds for NAntContrib aren't correct. If someone has
these files that would be appreciated.
thanks
brant
When compiling with devenv it will overrite the output assembly regardless
of its file attributes (ie: ReadOnly). The solution task does not do this.
Here is a patch to synch the two behaviours:
NAnt.VSNet/Project.cs
//THIS LINE MAKES THE OUTPUT FILE WRITTABLE
System.IO.File.SetAttributes
We solved this problem by creating a tool to update the .user files for
each developer. It scans the directory tree and then creates a .user file
for each .proj file with the correct reference path for that workstation.
brant
...
From: Martin Aliger [EMAIL PROTECTED]
To: Matthew Mastracci
if they modified NAnt in some way?
brant
...
_
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
---
This SF.net email
I was having this same problem! Thanks for the script.
+1 for a ant task
brant
...
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [nant-dev] New to the list
Date: Fri, 19 Mar 2004 08:57:55 -0500
Hi everyone! I joined this list because there are some differences between
Nant
In the 0.84 build there is a bug (keep forgeting to get an official patch)
where the solution task will fail if the output assembly is read-only on the
drive.
Normally you would think this is the desired behaviour but it is different
that what VS.NET does. We actually rely on this bug to make
16 matches
Mail list logo
