From: Vagmi M. <vag...@gm...> - 2005-02-07 09:44:00
|
RemoveFile table will still be a better solution that using a custom action to remove files. Even if the WIX Toolset has the bug, correcting it in orca or manually changing the compiler.cs and rebuilding the WIX toolset is not a big deal. I would still recommend the use of the RemoveFile table over a delete files custom action. On Mon, 07 Feb 2005 09:07:09 +0000, Robert Hamflett <ro...@sn...> wrote: > If these files are being created by Custom Actions, you need to write CAs to > remove them. You need to schedule them with an condition like "REMOVE=ALL" > so that they are run only on uninstall. Of course you need to remember to > put a condition on your original CAs so that they only get run on > installation, e.g. "Not Installed" > > Rob > > Michael Sperber wrote: > "Bob" == Bob Arnson <sf...@bo...> writes: Bob> The problem is that your > components don't have their Guid attribute set. MSI Bob> will happily > install GUID-less components, but then promptly forgets it ever Bob> did so. > [...] Many thanks---that helped! Next question: the installation generates > a few files by running a bunch of scripts. Of course, these don't get > deleted by the regular uninstalled. Can I somehow get msiexec /x to > uninstall these as well? > > -- The views expressed in this message do not necessarily constitute the > views of SN Systems Ltd and information in this message is confidential and > may be privileged. It is intended solely for the person to whom it is > addressed. If you are not the intended recipient, please notify the sender > and please delete the message from your system immediately. -- Vagmi http://geekswithblogs.net/vagmi.mudumbai http://installneo.blogspot.com |