I realize this is a certifiable Bad Thing(tm), but it's a situation I
haven't much control over. Here's what's going on.
Deployment crew deploys website or application .msi's to one set of our
production servers.
Instead of using the .msi's on all our redundant servers, they xcopy it
over to multiple other servers.
Next month, deployment crew does the same thing except that they start
on a different server, one of the xcopy servers. So the new .msi does
not overwrite anything on that server. Then they xcopy it to the
original server and regress everything back to where it was last month.
Everyone spends half a day trying to figure it out before anyone asks CM
about the installers. Problem is then discovered in about 10 seconds.
CM gets blamed for having bad installers.
I've suggested they 'use the installers correctly' but apparently this
is too difficult.
There is no 'extra stuff' in any of the directories, so if I could wipe
them out completely before the .msi starts <InstallFile ...> it would
solve this 'problem'.
Essentially I'm looking for a way to delete items that are not in the
file table in an installer prior to installing. I've tried <RemoveFile
... /> but it doesn't seem to work in the way I would like it to. Or
else I'm not doing it right. Any ideas?
----------
Matthew Janulewicz
SCM Engineer
Green Dot Corporation
[EMAIL PROTECTED]
(626) 775-3857
-------------------------------------------------------------------------
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
