Alexander Stock wrote: > So this weird issue is only happening because we're breaking component > rules? >
I can't know for sure without more details, but it's certainly possible. Successful patching relies on strictly following the component rules, because patching itself relies on proper component composition. > Whats the best (and easiest) way to manage patch-/setup creation of a > product that changes it (data-)file subset from version to version? > (In every new version we've some new and some obsolete files) > MSI patching isn't optimized for that kind of version-to-version change. You can update existing files easily. You can add resources with some restrictions. Removing, not so much. If that's a requirement, I'd recommend avoiding patches. Unless you have a large product and benefit from shipping only updated content, major upgrades will let you do everything you want. An alternative is to change your code to match your servicing technology: Don't rely on deleting files; instead, update files without changing their names. > Its not possible to remove components via patches, right? Therefore we > can't create for every file a component. Your problem is essentially the same regardless of the number of files per component: You can't remove components in a minor upgrade and you can't remove files from a component without breaking component rules. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
