Ok. This isn't really the behavior I'm looking for. I managed to solve my problem by using Components with empty GUIDs to install and modify the config files. In that way, the component is not managed. Since it cannot be updated or removed, my config files are not overwritten on upgrades any more. And I manage the remove part with RemoveFile elements.
Thanks for your help. Fred Stefan Krueger [MVP] a écrit : > I'm not sure about the WiX syntax but in MSI terms: if the component > condition evaluates to FALSEthe component will NOT be installed. And if it > was True in the first time install and then becomes False in the upgrade, > that component will be REMOVED - but only if the component has the > transitive flag set. Otherwise the condition willö not be re-evaluated. > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
