I haven't tried to solve this problem and I may be over simplifying some part of it, but have you considered using the NantContrib tasks to automatically register your library/framework binaries to the GAC? If these projects registered the latest successful outputs to the GAC each time they ran, then any dependant projects that needed those libraries would be able to get to the latest version whenever they were built.
If the GAC isn't an option, what about copying the binaries to a common location when each build executes and then referencing that location when building a dependant project? Similar idea to the GAC, but you wouldn't have to mess around with strong names and such. Just a thought. Tony <><><><><><><><> Problems get injected as products are coupled - one product_s output may be used in the next product as input (base library), especially as, along the product lines, we have an application framework and an O/R mapper among the products, having basically a100% reuse rate. ------------------------------------------------------- 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
