Thanks for the heads up. I'll bear that in mind. Presumably, changing the root folder for the files each time would solve this problem then.
so sample-v1 sample-v2, etc would fix it as the root of the installed pieces. Anthony Wieser Wieser Software Ltd ----- Original Message ----- From: "Mike Dimmick" <[EMAIL PROTECTED]> To: "'Anthony Wieser'" <[EMAIL PROTECTED]>; <wix-users@lists.sourceforge.net> Sent: Tuesday, May 22, 2007 12:17 AM Subject: RE: [WiX-users] Using heat.exe as part of an automated build process > Yes, you're breaking rule 1 of the component rules: a file installed to > the > same location must always belong to the same component and have the same > GUID. Change the GUID, it's a new component; change the component, you > must > change the final path name of the file. If you don't, you mess up Windows > Installer's reference counting and it may either remove files prematurely > or > not remove them when it should. > > At the very least you restrict where you can schedule the > RemoveExistingProducts action when performing an upgrade (if you do it > after > InstallFiles in the new product, Windows Installer will happily remove all > the old components - and the files it's just installed). > > -- > Mike Dimmick ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
