John Robbins wrote: > While the documentation says that there can be "(min: 0, max: unbounded)" > RemoveExistingProducts under the InstallExecuteSequence element, if you try > it, you get a "Duplicate symbol > 'Actions:InstallExecuteSequence/RemoveExistingProducts' found." error > compiling. >
Um, er, yeah. I don't know why the schema is set up that way. There isn't an explicit minOccurs/maxOccurs for RemoveExistingProducts so I'd expect the defaults to be 1/1 (per the XSD TR). But that doesn't seem to be the case...?! WiX schema aside, what counts is the MSI schema. The InstallExecuteSequence table's primary key is the Action column, so any action can appear only once. What you're proposing is an interesting optimization, but it's not something MSI supports. -- sig://boB http://bobs.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
