If the old installer didn't update the SharedDLLs reference count in the
registry, then there isn't a lot you can do.
Windows Installer updates this if requested, and if installing into certain
known locations. When uninstalling a component, if there are no more Windows
Installer references to the key file, it checks this registry key and if
present, decrements it. If the count has dropped to zero it removes the
files from the component.
If the file isn't the key file, I think you could have problems. The
consequences of a lot of the Windows Installer rules suggest that you should
only have a single file in a component, and there should definitely be only
one executable file in a component, and it should be the key path.
--
Mike Dimmick
_____
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bryan C.
Boettcher
Sent: 22 January 2008 18:07
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] MSI removing system file on uninstall
An older version of our product was installed with Internet Component
Download. Part of the install copied a .DLL to System32.
Our MSI installer of a newer version of the product copies the same version
of the DLL (it's a shared component that hasn't changed in a long time) to
System32. If the old version of the product is installed, and the MSI is
installed then removed, the old version of the product won't work anymore.
The MSI removes the file in System32. Is there any way to correct this
without marking the component Permanent?
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
