Hi all,

In our current build process we use Nant, and have the following configuration:

• Each solution has an associated build file, that builds only that solution and places the dll in a shared location. Developers run this build file when they have made a change to ensure their modification does not break the build.

• We then have a master build file, which calls each individual build file (of each solution that make up the program) in order of dependencies to build the full program.

In this situation I would err on the side of having a build type for each solution to ease the desktop scenario and then have an all encompassing build type that builds all of the solutions which could be used for dailies and/or continuous integration.

Thanks William,

An issue that relates to this approach is whether to have a Build Type that is a single entity and builds all the solutions for the program, or a master Build Type that runs a number of "Exec" task to run each individual solution Build Type from the command line in order. The second approach would directly link each individual Build Type to the main build process, and ensure any changes to an solution Build Type will be picked up in the main build. However in such a scenario

Team Build does not lend itself to the "master" build type approach, so I would counsel against trying to get something like this working - you'll run into lots of headaches. William's idea of simply having a separate build type that includes all of the solutions (rather than driving other build types) is probably your best bet. For the desktop scenario, it might be sufficient to skip the build types altogether and just have developers use VS / MSBuild to build individual solutions... Team Build doesn't do much more than this in a desktop build scenario in any case.

-Aaron