Hi Ruben, Yes, I do msbuild <solutionfile> but...
1) I have a project file for A, another for B, another for C, another for D and another for X. Each project has a solution file and each one is monitored and built with CCNET. 2) I have a global solution that includes projects A, B, C, D and X with their corresponding dependencies. However, this is only used for Release builds. I have no problem with point 2, I force a build and the release is built fine. Problems come with the first point and the unnecessary rebuilds. As I said, this can be solved by removing dependencies on ccnet.config file and getting something like this: A -> B B -> C C -> D D -> X X But, what happens if I remove project D? A, B, and C won't be built when X changes. That's a maintenance issue and my real projects structure is more complex. Cheers, Raúl On 1 abr, 13:10, Ruben Willems <ruben.will...@gmail.com> wrote: > Hi > > I think you do now msbuild <solutionfile> > and in this solution file you have projects A, B, C, D and X > with the defined dependencies. > > what can be a solution is the following : > ° manually determine the dependencies > ° call msbuild on each separate project > > this off course must be done in a build script, > so for the developers nothing changes, only the buildscript used by ccnet > will first pre-parse the sln file and do the actual build on the individual > items. > > with kind regards > Ruben Willems > > On Wed, Apr 1, 2009 at 12:59 PM, Raúl Nuño <rauln...@gmail.com> wrote: > > > I have been looking for solutions without success. > > > I will be brief. An example of my problem: > > > A -> B, C, D, X > > B -> C, D, X > > C -> D, X > > D -> X > > X > > > You can imagine what happens when the project X is built... D builds 1 > > time, C 2 times, B 3 times and A 4 times. > > > When I modify the dependency tree to get something like this, I solve > > the problem but it's not a good solution (maintenance issues). > > > A -> B > > B -> C > > C -> D > > D -> X > > X > > > Is there any solution?
