John,
We should .. euhm .. could ... (never say should, if there's a slight chance
that Ian is gonna read the mail .. LOL) also move to a fixed version number
for releases, now that all assemblies are built using a common
assemblyinfo.cs file.
I'll set a fixed version in src/CommonAssemblyInfo.cs
I John,
I never had any issues with these tests, can you possible debug the tests to
see what's actually happening ?
I would still like to get a few things in the 0.8.3 release : upgrade to a
new version of #cvslib, perhaps upgrade to a yet-to-be-released version of
log4net (which now uses the sa
> The following tests FAIL when attempting to build from the latest CVS.
Sorry, I should mention the build environment is Windows XP running the
net-1.1 framework. I will be installing Mandrake 9.1 with Mono 0.24 to test
the linux builds. Tests results in other environments would be really
helpfu
Since I'll be manhandling the 0.8.3 release, I thought a note introducing
myself would be in order.
I'm the Senior IT Developer at Grosvenor Financial Services in New Zealand.
My employer has kindly consented to let me contribute to the NAnt project on
company time. Personally, I have 10 years of
I'm hoping to do an 0.8.3 release sometime next weekend. Before we can
release, however, we'll need a clean build.
The following tests FAIL when attempting to build from the latest CVS.
If no-one fixes them before I wake up, I'll probably send in a patch or
two. Note that they're ALL failing on t
Ian,
why not simply add also the posibility to define a fileset as read-only,
just like properties, so if a master build file define a fileset and doesn't
want it to be changed the master buildfile could simply set the fileset as
readonly...
just and idea!
Nick
From: Ian MacLean <[EMAIL PR
Tom,
not to be a killjoy but what about having all sub projects output to a
common "build" directory then the filesets for assemblies and doc are as
simple as:
looking at your assumptions I've just realized that the list of datatype
references isn't getting passed to nant calls - I'll
Hi Ian:
Here's a scenario:
1. You have a product that has a cascading set of sub-projects.
2. Some of these sub-projects are company wide class libraries used in
more than one product line.
3. You have a product master.build file that will build the product.
4. Your master.build file calls int
Matthew Mastracci wrote:
I noticed some people talking earlier about having "build events" on
the solution task. Perhaps it might be useful to add each file, as it
was compiled, to a named fileset and run a task (such as FxCop or
obfuscation) on all the files after. What do you think?
We cou
I noticed some people talking earlier about having "build events" on the
solution task. Perhaps it might be useful to add each file, as it was
compiled, to a named fileset and run a task (such as FxCop or
obfuscation) on all the files after. What do you think?
We could probably do it by writi
how do you mean ? do you mean with code -inside a task or in the build
file itself ? Right now you could add to a named fileset using code -
since all references to a given type id are using the same instance of
the fileset. This is due to an implementation detail that may change
however.
Insid
Is it possible to add files to a named fileset once it has been created,
or do you need to recreate it?
Matt.
---
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicate
12 matches
Mail list logo
