n tasks in that generated file.
http://nant.sourceforge.net/release/latest/help/tasks/style.html
http://nant.sourceforge.net/release/latest/help/tasks/include.html
Ryan Davis
Acceleration.net
Director of Programming Services
2831 NW 41st street, suite B
Gainesville, FL 32606
Office: 352-335-6500 x
You could also run the build using the and then have a
to but the binaries where you want.
Ryan Davis
Acceleration.net
Director of Programming Services
2831 NW 41st street, suite B
Gainesville, FL 32606
Office: 352-335-6500 x 124
Fax: 352-335-6506
Brass Tilde wrote:
I am building a
You can also use this property:
Thanks,
Ryan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gary Feldman
Sent: Thursday, November 10, 2005 4:34 PM
To: nant-users@lists.sourceforge.net
Subject: Re: [Nant-users] use .net 1.1?
John Cole wrote:
>Is there
solution.
-scott
>From: "Ryan Davis" <[EMAIL PROTECTED]>
>To: "'Scott Clemmons'"
><[EMAIL PROTECTED]>,
>Subject: RE: [Nant-users] deploying asp.net applications
>Date: Fri, 4 Nov 2005 09:51:40 -0500
>
>Not necessarily common, but one w
Not necessarily common, but one way just popped into my head:
Store your application in a new directory every time you publish a new version,
and then change the IIS entry to have that web app
point to the new directory.
The process would become:
1. Build the new version
2. Zip the new version
Title: Exec program can't handle dir name with spaces
This is a command line
issue. You're essentially
executing:
C:\>changes.cmd root
branch tstamp > c:\builds\smc management center\logfiles\filename
So it's not
reading the whole path for the pipe, just the "c:\builds\smc", and
then
Looking at the nant-contrib source for the task, you could do a commit by
specifying a Command of "commit". The task is just
translating the options into a command line call to svn.exe. I found using an
to be simpler.
Thanks,
Ryan
-Original Message-
From: [EMAIL PROTECTED] [mailto:
Well, I think that comes down to a cost/benefit analysis. If the benefits of
building with NAnt outweigh the cost of learning, then
your developers will likely hop on the bandwagon.
I phased it in at my workplace, where we do mostly web apps. Our devs use
VS.NET for coding, testing, and debugg
Getting a little off topic, but you mentioned using the script as documentation:
>> Indeed, a reasonably well written NAnt script could even (with a small
>> stretch of imagination) be considered to be the documentation.
>> Even if you aren't familiar with the structure of NAnt, something like
>>
I'm not sure how to
solve that, but you should really consider moving to Subversion for source
control. There are some nant-contrib tasks that work very nicely with it, good
windows client support via TortoiseSVN, tight visual
studio integration via Ankh, works well with Cruise control, an
I think that is saying that your version of NAnt was compiled for version 1.0.
Thanks,
Ryan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, June 14, 2005 10:32 AM
To: nant-users@lists.sourceforge.net
Subject: [Nant-users]
I get this error all the time. To the best of my knowledge, Visual Studio is
opening the DLLs to read meta-data for autocomplete,
and not cleaning up after itself.
My coworkers have researched this problem extensively and found a dubious fix:
http://blogs.acceleration.net/russ/archive/2004/10/17
I solved this problem by making an xslt to convert the .csproj file into a file
list, then use the task to copy the files.
The XLST is attached, and here's a simplified version of my nant task (not
tested):
So the
I solved this problem by making an xslt to convert the .csproj file into a file
list, then use the task to copy the files.
The XLST is attached, and here's a simplified version of my nant task (not
tested):
So the
Title:
Looks like it might be
a bug in your included build file.
This is exactly what I
do, except I have the project's build files setting a lot of properties, and
the master build file makes all its decisions based on those properties.
I'm not sure how
overriding targets would
This is starting to get a little OT, but here's how we have it set up.
The programming dept. of our company is pretty small (4 programmers and 3
designers) and we do mostly consultancy stuff (mostly
websites), so that means a ton of separate projects, and a few libraries we use
across all projec
Could one be doing a
debug build and the other a release?
Thanks,
Ryan
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: Monday, February 07, 2005
9:58 AM
To:
nant-users@lists.sourceforge.net
Cc: Gert Driesen
Subject: RE: [Nant-users] d
Another option would be to use the xmlpeek
(http://nant.sourceforge.net/release/latest/help/tasks/xmlpeek.html) to read
values from
an xml file. That might end up cleaner, might not.
Thanks,
Ryan
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adrian
2. To get around this problem, I created a "lib" folder in my project, and
added the reference to there. This makes a relative
path in the project file, so whenever someone gets the project, they
automatically have the libraries. I think it might do that for
anything in the solution directory
You could also make it an xml file and use the task. If you end up
with many of these values, it might get a little messy
to have a one-line text file for each.
http://nant.sourceforge.net/release/latest/help/tasks/xmlpeek.html
Thanks,
Ryan
-Original Message-
From: [EMAIL PROTECTED]
1. A
2. I use to compile my projects, and have the references
sorted out in my Visual Studio projects in a solution.
3.
4. Usually compile with VS, finding syntax errors is easier from its task
list, and then run the tests with Nant in a command line window. I have my
tests in a sepe
21 matches
Mail list logo
