You'd use conditional property assignment.
First set the default property value, then conditionally re-assign it if
your condition is met. So:
property name=some.target value=some.target2 /
property name=some.target value=some.target1 if=${CCNetBuildCondition
== 'ForceBuild'}/
---
X
Continuous
I went through a similar process a few years ago and decided to switch from
Token Replace to XML Poke. I think you've done a good job of documenting the
strengths and weaknesses of each approach. in general I think XML Poke is
cleaner. The only real problem I found was that XML Poke wouldn't work
We have set up an environment where we can conditionally rebuild components,
if they've changed without having to rebuild the entire system. Doing so
requires careful management of dependencies. If an interface or common
datatype changes, then you pretty much need to rebuild everything. But if
the
. Isn't that possible?
On Tue, Jun 21, 2011 at 1:28 AM, Christopher Brandt
xtopher.bra...@gmail.com
mailto:xtopher.brandt@gmail.**comxtopher.bra...@gmail.com
wrote:
Have you tried moving all of the dependencies (ie,
Should.Fluent.dll ) into the same directory as the executable
Have you tried moving all of the dependencies (ie, Should.Fluent.dll ) into
the same directory as the executable?
---
Chris.
Continuous improvement is better than delayed perfection. - Mark Twain
On Mon, Jun 20, 2011 at 12:13 PM, Heintz, Aleksander alxa...@alxandr.mewrote:
I'm having trouble
We rely heavily on NAnt and I fear it would be a major under-taking to move
away from it.
We've had no problems with it until .Net 4.0. Luckily, we can build on our
build server, but I get the mysterious security exceptions when trying to
build on my local machine. That problem does need to be
I'm stumped on how to get a mono build of a C# project with NAnt. I'm using
the 0.90 build.
The problem seems to be that NAnt isn't passing the reference assemblies
through to gmcs.
Attempting to building the following file with NAnt results in the error:
[csc] C:\Temp\HelloMono\hello.cs(3,14):
To clarify, by regular cruisecontrol do you mean you're not using
CruiseControl.Net?
---
Chris
Continuous improvement is better than delayed perfection. - Mark Twain
On Tue, Nov 16, 2010 at 8:00 AM, Adam Bruss abr...@awrcorp.com wrote:
Thanks but I’m trying to use nant from regular
I've found one more problem and solution to it but also have a puzzling
situation.
First the problem; on our build server we're running NAnt 0.86 and I'm
trying to get things working with the net-3.5 target framework. One build
was failing with an error:
Unexpected attribute if on element
, build server is using V2.0 and my desktop is
using V3.5?
Thanks
---
Chris.
Continuous improvement is better than delayed perfection. - Mark Twain
On Mon, Mar 22, 2010 at 8:29 PM, Christopher Brandt
xtopher.bra...@gmail.com wrote:
Sorry, an important bit of info there: NAnt 0.86 on both my
This is related to my previous post on Windows 7 VS2008.
After some help I realized that the target framework on my desktop was .Net
3.5 whereas on my build server (Windows 2003 Server) it was .Net 2.0. The
was causing some problems between the two environment in how csc.exe was
importing
wrote:
I use the latest nightly and it works ok. But, I explicity let the
targetframework property in the scripts.
I also use the msbuild task rather then the csc task.. but I assume it uses
the same mechanism to determine which to use.
BOb
*From:* Christopher Brandt
What's the rationale for inclusion in the list of reference assemblies for
each target framework? I'm looking at the NAnt.exe.config file again.
It appears to be a complete list of all the framework libraries. If it is
then the list is missing:
System.DirectoryServices.Protocols.dll
Which I
I've recently upgraded my desktop to Windows 7 and have installed VS2008 (no
other versions). Our build server is still running Windows Server 2003 with
MS .Net Framework 3.5 SP1.
Our software uses WCF and we've always had to to reference the
System.ServiceModel and System.Runtime.Serialization
the compilers located on the machine. It doesn't come
with its own.
On Mon, Mar 22, 2010 at 4:06 PM, Christopher Brandt
xtopher.bra...@gmail.com wrote:
I've recently upgraded my desktop to Windows 7 and have installed VS2008
(no
other versions). Our build server is still running Windows
15 matches
Mail list logo
