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
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
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
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:
fileset id=ass-dll-fs
includes name=*.dll /
fileset/
and
fileset id=ass-doc-fs
includes name=*.xml /
fileset/
looking at your
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
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
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
