depending on your usage, it might be that the directories list is
pretty static, however one advantage of the solution file is that you
can change the list of dependent projects that are included - in this
case, you have to make sure you mirror the changes both in the project
file and in the NAnt script.
also, if you make changes in how you build/install/package up your
projects (maybe some use non-default directories, or have additional
pre/post build steps, etc), it would be nice to not have to go change
your NAnt scripts
also - it would be great if there was some property or value exposed
from the solution task or somewhere that gave you the list/location of
the bin/obj directories as specified in the .NET solution/project
files, so that even if you had to write NAnt script to parse that
property and delete the list of dircetories, at least you'd know that
you were removing the right things, since there would be a single
source of the data in question.
it's not impossible to do manually, of couse, but it's one more thing
that has to be included and done manually, since it's a separate config
file for a separate tool, and thus it's something that can be
forgotten, so if it were possible to automate, it would be less error
prone.
- [Nant-users] solution task and clean target noshyuz
- Re: [Nant-users] solution task and clean target Gary Feldman
- Re: [Nant-users] solution task and clean target noshyuz
- Re: [Nant-users] solution task and clean target Gary Feldman