Any suggested tactics to deal with this? sorry for the newbie question but i've been looking around for some documented advice and haven't found any luck so far.
My problem is that we are constantly introducing new projects and new dependencies. It seems like maintaining a buildfile in such an environment is going to be a nightmare. I've been trying out the Nant "Solution" task and tried chaining project buildfiles that mimic the current dependencies so if someone introduces a dependency in a commonly used project, I just need to add that new dependency in 1 location and the new dependency will propogate to higher level buildfiles, but I’m not having any luck.
One of the nice things with Visual Studio Solutions was how a user could selectively build a project and Visual Studio would figure out all the relevant dependent projects from all possible dependent projects included in the solution file
Is there any similar capability in Nant where you can specify the main project that is required + a list of all possible dependent projects? From the list of all possible dependent projects Nant could dynamically figure out the minimum dependent projects to compile. Is something like this currently possible in Nant?
If my above idea isn’t doable does anybody have any other suggested tactics on how to tackle a build environment where new cs project dependencies are constantly added in a very fast paced environment?
thanks in advance
Joon
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
