Keith Kaminski wrote:
I’m working in an environment where developers will often choose to
build only one or two projects at a time within a solution that has
nearly 50 projects. Although we ask them to make sure that they only
check in a solution file where all projects are set to be built, this
doesn’t always happen. This often screws up the build process, and
though it’s pretty easy to fix by hand, I’d rather not have to do it
by hand. I know that I can specify which projects to include with the
<projects> tag, but we add projects to our solution pretty regularly,
and I’d rather not have to update our NAnt build every time this
happens. So, I was wondering if it were possible to force a build of all
The projects tag is a subtype of fileset, which means that wildcards
should work. So something like
<projects>
<include name="**/*csproj" />
....
</projects>
ought to get everything.
In the long run, though, you may be better off partitioning your system
and adding more solution files, so that developers aren't tempted to
disable builds. This will make things more manageable overall. Then just
have one solution file for the build that the developers don't change.
This will speed up Visual Studio responsiveness in other ways, so the
developers shouldn't mind.
Gary
projects within a solution file using a <solution> tag without having
to individually specify every project. Or, if there isn’t a way to do
it through the <solution> tag, if anyone has a slick solution to this
problem.
Thanks in advance!
- Keith
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
