Hi there, I understand from Rob's blog entries that it is recommended to have a single file per component. And if this recommendation was followed I wouldn't be in the situation I am in. Also, having a file with the version number in the filename as keypath (and is bound to change for the next release) isn't great either. Regardless, here is the problem I am facing: We have shipped an installer which has a component containing multiple files. The keypath is one of these files called zxc-1-30.jar The problem is that the next release needs to replace zxc-1-30.jar with zxc-2-45.jar, but leave the other files intact. Unfortunately the component authoring rules are marking all files in the component for removal (including the files that I would like to keep). The removal is sheduled to happen afterInstallFinalize. My first attempt to solve this was to schedule the RemoveExistingProducts action earlier (which solves the problem) - but a side effect (user customized files being removed) is not great. I understand that I can create a custom action to copy user customized files out of the way - but this seems like an ugly workaround. Another option might be to use a different directory for the files in this component in the next release - also not great. Am I missing an obvious fix? Can anyone suggest another solution? Regards,Simon ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
