Re: Cleaning up files after MSI uninstall

I don't know whether WISE/MSI might have a better
solution, but I would think you could just install dummies.
In other words, install a dummy file as a placeholder
for the one that will be created and create Registry
entries at install time that will be used later.

On the other hand, it's "traditional" not to uninstall
created files. Most installers, in my experience, will
just leave the Program Files folder behind with the
new files in it if they're not on the uninstall list.

I'm not sure if the word WISE deterred anyone to respond...so...just in
case....

Anyone have good solution to removing "non-shared" program files and
directories after unintstall of MSI package..(which I'm currently
deploying
via GPO software installation)

Thanks.

Shawn


"shawn" <shawnl.liggett@xxxxxxxxxx> wrote in message
news:eBgA2%23DpGHA.524@xxxxxxxxxxxxxxxxxxxxxxx
All,

Created MSI install with Wise Installer for Windows for a VB6 Outlook
Addin.

After deploying application...and user running addin...additional
registry
entries are added into HKCU area and additional directories and files
are
placed in application directory.

Question: When uninstalling the application, I want to "clean up"
registry entries and files/directories that are "left behind". Wise
does
not appear to give you option to remove registry entries/files that it
did
not install. What is the best way to achieve "clean up" for a project
built with Wise? (i.e. MSI script, "run once" script, Wise custom action
script. etc)

I've been searching for couple days and have not come across a valid
solution...yet.

Any direction would be appreciated.

(More info can be provided as needed)

Thanks in advance.

Shawn





.

Relevant Pages

  • Re: logon script
    ... I believe you will not be able to install software for the user using the ... Then in the vbs call your msi package with all the switches. ... Windows Script Host ... wanted to just create a GP pointing to a login script. ...
    (microsoft.public.windows.group_policy)
  • RE: import msi failed
    ... after refreshing the script ressources and rebuild the msi it works fine. ... What you are seeing may be a related to a bug in the Beta version. ... the same mismatch occurs on install. ...
    (microsoft.public.biztalk.general)
  • Re: logon script
    ... Windows Script Host ... bomb saying that there was nothing there to build the MSI. ... How should a script install a product, ...
    (microsoft.public.windows.group_policy)
  • Re: commands not waiting, /wait not helping
    ... >smaller install programs, and I wanted to ensure the included projects were ... >current before compiling the main one. ... The START command hates the quoted parameters. ... >> For Wise, like most application, I always install it in a simple ...
    (microsoft.public.win32.programmer.tools)
  • Re: commands not waiting, /wait not helping
    ... smaller install programs, and I wanted to ensure the included projects were ... batch files, but apparently never checked to see that it waited and actually ... The START command hates the quoted parameters. ... > For Wise, like most application, I always install it in a simple ...
    (microsoft.public.win32.programmer.tools)