Title: csc Task Strategies
There
are ways to simplify your problem, depending on your circumstances. I am
assuming that your assemblies are strong named, so you need to reference the
specific version? Does the whole system always reference a single version
of a particular assembly or could
Ken Witmyer wrote:
The developers are understandably not too keen on the idea of manually
maintaining these references in the build scripts. They have proposed
hooking into VS.NET's build process to mine the .csproj files and
rebuild the csc tasks in the build scripts. I'm a bit hesitant
be
Title: csc Task Strategies
We have a similar issue with both references and files.
In some cases developers were checking in files that weren't included in the
csproj file, but would get picked up by the csc task fileset (**\*.cs). To
resolve this we built our nant scripts to parse the csproj
Title: csc Task Strategies
I have
tried fixing a vaguely similary problem. My solution was far from
perfect, but does make the maintenance task slightly easier. I have
created a separate build script for each assembly and then a master script
that refers back to the separate scripts. This
