> I've been trying out the Nant "Solution" task I am not 100% certain I see your exact problem clearly, but let me throw this out there and see if it helps.
I work for a consulting services company, so we have many, many projects that all have different and frequently changing dependencies. I actually use just one default.build Nant file for all of our projects (with a few very odd exceptions). This file is passed the name of the VS solution file and uses the <solution> task to build the entire project set in the proper order. Since the altered dependencies are always within the VS solution file, the build file itself has no need to be aware of them. The only place that this becomes a little tricky is with web projects, because you can't dynamically build/set the <mappath> values. For this, I use a solution-level file in Visual Studio called mappath.config. When the Nant build file runs, it looks for this file in the working directory. If it finds it, it opens the file, reads in the delimited virtual/physical mappings, dynamically builds a small, external Nant build file and then calls that external file to do the <solution> build before continuing with the main file. As long as the dependencies that you refer to are maintained within the VS solution files, this system should work for you. If, however, you have external dependencies that are not included in the solution as a project or external reference, then this may not help. Tony ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
