That worked perfectly. Thanks!

Andrew

On Tue, Jun 15, 2010 at 3:40 PM, Blair <os...@live.com> wrote:

> If your base XML file (as shared by all three products) is fairly static,
> you should be able to create a shared component (a component where the GUID
> and the directory are the same for all three products). If your XML
> "transformations" can be applied in any order, you shouldn't have any
> problem using them (you will need to have them be in a different component
> than the shared component, unique to each product). If those components
> include "removal" instructions, you should be able to easily add/remove
> products easily.
>
> If any of your transformations need to change the same node in your base
> XML, you will have some additional work that may require a custom action to
> read the current file to compute the new value(s) to use.
>
> -----Original Message-----
> From: Andrew Hammond [mailto:andrew.george.hamm...@gmail.com]
> Sent: Tuesday, June 15, 2010 10:42 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] shared config file clobbering
>
> I have an XML config file which is shared by three products. Each installer
> currently uses util:XmlFile actions to put appropriate information in the
> config file. When only one product is installed, this works fine, but when
> two or more are installed, the last one installed clobbers the config of
> any
> others. What I would like is for any of them to install the base file if it
> doesn't exist and then to apply the xml transformations so that the end
> result is a merge of all the transformations involved. These
> transformations
> are idempotent and discrete. Is this a reasonable approach or is there a
> better solution? The other idea I had was to have the file be in a separate
> installer and then have the other installers depend on it and only run the
> transformations. Can anyone please offer advice?
>
> Andrew
>
> ----------------------------------------------------------------------------
> --
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to