Andy, If you have a RemoveExistingProducts action scheduled in one location in your common element and another scheduled elsewhere in your Product consuming the common WiX I'm pretty sure you would get a compilation error.
You could set something up in your common WiX fragments/include to conditionally include the RemoveExistingProducts action at both sequence locations based on a WiX preprocessor variable and have a default location preferred that could be overridden to the other sequence location by setting that preprocessor variable in the consuming WiX. -Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Best-Practices-Using-for-GUID-automation-tp5234716p5608434.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
