integrating ncover into
dailybuild with nant.
Morris, Jason wrote:
Where did you get NCover from?
http://ncover.org/
- or -
http://ncover.sourceforge.net/
IIRC, I had this problem when I used the version from
SourceForge, but
if you go to ncover.org, that version seems to work a lot better
Where did you get NCover from?
http://ncover.org/
- or -
http://ncover.sourceforge.net/
IIRC, I had this problem when I used the version from SourceForge, but
if you go to ncover.org, that version seems to work a lot better. Plus,
I found ncover.org's version integrated with nAnt a lot
I believe that this was the same problem that I ran in to. Gert has posted a
fix for this, but you will have to download a nightly build. The first one
that I got to work was the nightly on 20-Apr.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 30, 2004 10:14 AM
To: Morris, Jason; nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] Request for version task patch be
committed (#1083618)
Hi Jason,
I've attached a modified
.
Jason
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Morris, Jason
Sent: Saturday, December 11, 2004 3:24 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Request for version task patch be
committed (#1083618)
Nant committers,
I would like my patch
I also want to give a big thanks to Gert and everyone
else who contributed to the latest nAnt release.
My group and I have had similar results upgrading from
0.82 and 0.83 to 0.84 as David mentioned.
We have utilized several of the new tasks into our
builds.
Thanks again!
Jason
From:
I haven't seen much bug traffic about rc1, so just curious as to what
the release plan/schedule was for .84.
Seems to be a lot of excitement for the expression evaluator
enhancements...is this delaying the final release of .84? Will it be
included in .84rc2?
Thanks,
Jason
PS. As always,
John,
Thanks for taking up this task...any further progress on releasing the
first beta or release candidate?
My vote would be for one distribution package with the binaries for each
.NET framework in separate directories. I don't think that we should
include the documentation or source in the
for mono (as mono progresses our available features are also
growing). Our goal is to provide binaries that meet the minimum
framework requirements. In the future I expect our compiled binaries
will run on mono out of the dist directly, just like they do on the ms
.net frameworks.
quote who=Morris
Just curious...
I know I can grab a nightly, but it is a much easier sell to others in
my group if I can say, We need to upgrade our build files to utilize
the new nant release. than to say, ...for the new nant nightly
Nightly to most people equates to unstable.
It's been 2 months since the
Driesen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 09, 2003 3:02 AM
To: Morris, Jason; Nant-Developers (E-Mail)
Subject: Re: [nant-dev] servicecontroller task
Hi Morris,
It should work with remote services, there's a machine (should I
rename it to server or computer ?) attribute that allows
Any chance to make this task work for remote services?
In my build/deploy setup, I need to stop/start/restart services on our
production box, from our build box. I currently use the exec task
with netsvc.exe so that I can specify a remote machine. I think I got
netsvc.exe out of the Win2K
My $.02
I think it is a very good idea to include nAntContrib project with the
nAnt release. I depend on a lot of tasks in nAntContrib and therefore
have a difficult time when nAnt releases a new version. I have to
figure out if the existing nAntContrib task will work or not and then
try to
Title: Message
On my
builds, I have a separate filethat just contains properties and nothing
else. For example,
?xml version="1.0" encoding="utf-8"
?project xmlns="http://tempuri.org/nant-vs.xsd"
name="Global Properties"
property name="isGlobalPropertyFileIncluded" value="true"
/!--
Aaron,
Try structuring your exec task using arg's
For example,
target name=build-database description=Install the database using
the CMD File
exec verbose=true basedir=${project.base.dir}
program=${commandfile.name}
arg value=${sqlserver.name} /
arg
I have multiple build files that I include into a master build file.
The build files have dependencies between targets in them. I would like
to be able to do something like this:
nant build -buildfile:file.build -buildorder
And out spits the order in which Nant would call the
16 matches
Mail list logo
