On 6/22/2010 10:29 AM, Stefan Kuhr wrote: > So what would then be a proper solution for my problem? I have PNG > files (so > theses are unversioned by definition) that I always want to replace with > those from my install, even if the customer replaced them with his own files > in the older version of my app that I am about to upgrade with a major > update.
Don't install files you expect the user to overwrite. If needed, install them in a protected directory (like Program Files) and copy them to a per-user directory. > I guess if I created each PNG-component with a new GUID with each new major > version that would break component rules, right? > Yes. > Would making the PNG files companion files of a DLL or exe, that I replace > with a new version in each major update, solve the problem? > Never tried it. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
