My suggestion is generally to use autoguids (aka: "*" GUIDs or in WiX v3.7+ (I think) just leave the Guid attribute off completely).
-----Original Message----- From: br...@dreamonsoftware.com [mailto:br...@dreamonsoftware.com] Sent: Friday, March 7, 2014 9:15 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Question about versioning with regard to GUIDs using a VS2012 project, and TFS build I am trying to manage the GUIDs in the component fragments using Project Output for binaries and content so that they remain the same for dll's/content between builds associated with project through the GUI. This also has to work through TFS MSBuilds as well. What is the best approach? Bruce Heath DreamOn Software br...@dreamonsoftware.com 989-785-9055 ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
