It looks like a simple Registry tag does the trick of removing it:
<Component Id="NukeISRegistryStuff"
Guid="B979D202-E062-46f2-93C7-81E9C36707E7">
<Registry Root="HKLM"
Key="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_{2C5BF41E-E2D3-4B2C-83F6-B42F29ABFFFF}"
Action="removeKeyOnInstall" >
</Registry>
</Component>
I had to drop RemoveRegistryValues into the InstallExecuteSequence as well.
Alexander Shevchuk wrote:
> Normally, that registry key holds a ProductName property:
>
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\[ProductName]
>
> So, your choices are either change your ProductName to match original from
> InstallShield or keep your current ProductName and remove that InstallShield
> registry key.
>
> Alex
>
>
>
> -----Original Message-----
> From: Michael Owings [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 14, 2008 1:11 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] Major upgrade from an IS12 installer project
>
> I am in the processing of moving from IS12 to Wix for a number of our
> products. So far, things are going fairly well.
>
> There is one issue, however. The install we have out in the field is
> version 4.0.17. I have done a Wix installer that does a major upgrade to
> 4.0.20. Everything works fine -- the old product ID is uninstalled, and
> the new one replaces it. I can verify this both through the logs and
> through the actual changes to the filesystem and registry.
>
> However, there is one remaining issue. It looks like a registry entry
> from the original IS install is left in:
>
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_{old-product
> code}
>
> This key while otherwise harmless, causes the Add/Remove programs panel
> in control panel to show an entry for the old product version. Of
> course, the old product can no longer be removed because it is no longer
> installed. Removing this leftover uninstall key from the registry fixes
> any issues.
>
> My questions are these:
>
> 1) Am I doing something wrong on my major upgrade to cause this key to
> not get removed?
> 2) If the answer to 1) is no, what would be the best way to go about
> removing this entry? I already have a number of C++ custom actions, and
> it would be fairly easy to add a new one to kill off that key if needed,
> but is there a better way?
>
> Thanx in advance -- mikey
>
> --
> Teleoperate a roving mobile robot from the web:
> http://www.swampgas.com/robotics/rover.html
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
--
Teleoperate a roving mobile robot from the web:
http://www.swampgas.com/robotics/rover.html
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
