>> http://trentm.com/blog/archives/2007/05/29/wix-and-msp/. The idea is >you replace the <File> element with a <RemoveFile> like the following: >> >> <Component Id='AnotherFile' >> Guid='C7D97EA9-83DF-4B07-8E38-D10A30F70FD2'> >> <RemoveFile Id='RemoveFile' On='install' Name='NewFile.txt'/> >> </Component> >> In my installers, I'm using patches to upgrade and the above trick >does work. >Do you do QFEs? I'm thinking that it's a component-rule violation >because you're changing the composition of the component. That'll bite >you when you get into supersedence.
I'm doing minor upgrades. In my case, when I do a major upgrade my product will be going into a completely different directory so I think I'm OK. >> If there are no good solutions for the removed files problem does that >mean that there's a flaw in the installer technology? >SxS and the component rules in general seem to assume a level of process >discipline that fits right in with the likes of Office or SQL but >nowhere else.<g> Hahaha! Great, that's just what we all wanted to hear. :) I can't help but think that it sounds like the whole patching system in Windows Installer is not really a viable solution for the real world. Bummer. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
