Matt,
This is probably late and you already found out by yourself how to use this tool, but the following text might be useful: To setup dependency replicator so that the outputs of the SystemAContinuous are replicated to $/SystemB/SystemB/Dependencies you would put the following configuration file in $/SystemA/TeamBuildTypes/DependencyReplicator.xml <?xml version="1.0" encoding="utf-8" ?> <Rules> <Rule BuildType="SystemAContinuous" EventType="New" Source="Release/ActiproSoftware.Ribbon.WPF30.dll" Destination="$/SystemB/Dependencies/ActiproSoftware.Ribbon.WPF30.dll" /> </Rules> NOTE: The tool expects $/SystemB/Dependencies/ActiproSoftware.Ribbon.WPF30.dll to exist in Source Control, Dependency Replicator won't add the file it will only do check-in/check-out The source attribute indicates where in the build directory (inside buildFolder\buildName\buildWithDateAndEverything\) the source is, this could be something like release, debug or Mixed Platforms depending on your solution configuration. Let me know if you have any problem and how could I help you. Beware of scenarios where SystamA copies a dependency to SystemB and SystemB is set to copy other dependency to SystemA because that will cycle the build. Miguel A. Madero Reyes Integradores Tecnológicos S.C. <http://www.integradorestecnologicos.com/> www.integradorestecnologicos.com <http://www.miguelmadero.com/> www.miguelmadero.com (blog) <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] (871)730-8319 (871)763-0020 Peten #509 Fracc Florida Blanca, 27260 Torreón, Coahuila P "Please reconsider your environmental responsibility before printing this e-mail" The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Lynch Sent: Thursday, September 04, 2008 5:38 PM To: [email protected] Subject: RE: [OzTFS] Team Build & Shared Lib Folder Hi Stephen, That looks like a really neat tool. You wouldnt happen to have a sample xml file for it? Theres no documentation, samples or code comments - reading the code to work it out is a bit slow. I guess free code is like a free puppy you cant complain when it pees on the rug. Im currently up to chapter: ExecuteDependencyReplicationRules(RuleCollection rules). Cheers, Matt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Godbold Sent: Thursday, 4 September 2008 4:57 PM To: [email protected] Subject: RE: [OzTFS] Team Build & Shared Lib Folder 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 youve got a CI build setup will kick that off and give you an _almost_ instant health check J http://www.codeplex.com/tfsdepreplicator Stephen Godbold Readify | Senior Developer M: +61 409 390 683 | E: <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] | W: <http://www.readify.net/> www.readify.net | B: <http://seesharper.wordpress.com/> 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, Ive 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 doesnt 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 its 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 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
