Take a look at Dependency Replicator. You can configure your dependencies in an xml file, then it will monitor the build status of the selected builds. On successful completion it will automatically perform a check out, copy and check in of the specified assemblies, which if you've got a CI build setup will kick that off and give you an _almost_ instant health check :)
http://www.codeplex.com/tfsdepreplicator Stephen Godbold Readify | Senior Developer M: +61 409 390 683 | E: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> | W: www.readify.net<http://www.readify.net/> | B: seesharper.wordpress.com<http://seesharper.wordpress.com/> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Guger, Larry Sent: Thursday, 4 September 2008 2:18 PM To: [email protected] Subject: RE: [OzTFS] Team Build & Shared Lib Folder Two ideas spring to mind. 1. Include the dependant solutions in the MSBuild script for the framework so that after the framework builds and copies its assemblies to the global location then goes and builds the dependant solutions 2. Have the MSBuild script for the framework add its assemblies to each of the relevant source control projects for each of the dependant projects (in a relative Lib folder perhaps) thereby kicking off a CI build for each? Regards, Larry Guger From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Lynch Sent: Wednesday, September 03, 2008 8:51 PM To: [email protected] Subject: [OzTFS] Team Build & Shared Lib Folder Hi, I've built a library which acts as a framework for several other solutions. When I make changes to the framework project, I would like to rebuild the dependant solutions. At the moment, each solution has a local Lib folder which has a copy of each assembly it requires. The strategy works well for solutions which are independent of others, but doesn't work well for this scenario. In the past, I have had a global lib folder, which contained the latest version of each assembly and all solutions would reference that folder and copy the output assemblies there when built. It was very simple, copying all assemblies from the output folder to the global lib folder, overwriting any older files. It worked well, except if the solutions were built in the wrong order. It was very easy for a older assembly to find it's way into the latest folder, thereby breaking a number of solutions in one go. There surely has to be a more stable approach. Any tips/tricks/comments/suggestions welcome. Cheers, Matt Lynch http://matt-lynch.spaces.live.com/ OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
