Hello,
An old version of our product's installation routine has created some
registry values that are interfering with the operation of our new
product version. These were created by a Custom Action running
regsvr32. The new installer of course uses output from Heat to
register the DLL in question correctly.
While uninstalling the previous version (which runs regsvr32 /u as a
custom action) fixes the problem, this is not a viable solution as
management has decided that we must allow simultaneous deployment of
the previous version with the current version.
Since I know exactly what keys are interfering, I was hoping to use
RemoveRegistryValue, but it does not seem to be working.
I have the following line in the component that registers the new DLLs.:
<RemoveRegistryValue Root="HKCR" Key="CLSID\{Our product's
GUID}\InprocServer32" Name="InprocServer32"/>
In this case, the value remains after the installation completes. The
MSI logfile shows that RemoveRegistryValue completed with a value of
1. The value is a REG_MULTI_SZ type, if it makes a difference.
Any advice?
Thank you,
---
Dan Moody | Deployment Engineer | Gibbs and Associates
Phone: 805-523-0004
Email:d...@gibbscam.com
www.GibbsCAM.com
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
