[wix-users] Issues when Major Upgrade an InstallShield package

[Persson, Magnus (SE-TLX)]

Thanks for your valuable information. I'll test a few ways to deal with 
the InstallShield scenario. The good thing is that once moved to WiX 
we'll have better control of the behavior.

Thanks again,
Magnus

On 2017-01-31 17:32, Wheeler, Blaine (DSHS/DCS) wrote:
> Plus 1
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Hoover, Jacob
> Sent: Tuesday, January 31, 2017 8:11 AM
> To: WiX Toolset Users Mailing List
> Subject: Re: [wix-users] Issues when Major Upgrade an InstallShield package
>
> If you deploy a bundle, you could put an exe package in the chain with a custom detect and install condition that would cleanup/remove your old install shield installation. This custom exe would be fairly easy to write, and would simply lookup your old installer (reg search or MSi* calls) to find the location and arguments needed to be passed to remove the old application.
>
> -----Original Message-----
> From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Michael Urman
> Sent: Tuesday, January 31, 2017 9:35 AM
> To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
> Subject: Re: [wix-users] Issues when Major Upgrade an InstallShield package
>
> Magnus,
>
> Your InstallScript MSI package is not purely from the world of MSI, so you shouldn't expect it to be removed solely with MSI's approaches.
>
> The action property of an Upgrade table entry is filled with the product code of any matching installer. For ease in detecting this scenario I would suggest altering your upgrade code in order to differentiate your pre- and
> post- InstallScript MSI packages from each other, and correspondingly adding a new entry to the Upgrade table. But even if you don't do that, you can look for and, if found, execute "C:\Program Files\InstallShield Installation Information\{ProductCode}\setup.exe /uninst". Note that as this will invoke Windows Installer, it cannot be called from the execute sequence of another MSI.
>
> Michael
>
> On Tue, Jan 31, 2017 at 4:22 AM, Persson, Magnus (SE-TLX) < magnus.persson at assaabloy.com> wrote:
>
>> We've been using InstallShield for 20 years and are frankly fed up
>> with all bugs and workarounds required to us it.
>> WiX is the perfect replacement but until the first upgrade (i.e. from
>> InstallShield to WiX) there are a couple of things I need help with.
>>
>> When I launch the new WiX package that will Major Upgrade the existing
>> InstallShield package, a dialog will popup during 'Validating install'.
>> This dialog will have a textbox with the text "Windows(r) installer
>> (Process Id: 4808)" and I can select 'Exit', 'Ignore' or 'Retry'.
>>
>> The only way forward will be to click on 'Ignore' which will cause the
>> upgrade to require a restart at the end (which is fine).
>> I assume this additional MSI process is some hack within InstallShield
>> but is there a way to prevent this scenario?
>>
>> After the WiX installer has finished there is still a leftover in the
>> ARP control panel applet and the reason for this is again an
>> InstallShield hack
>> (HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\InstallShiel
>> d_{
>> Product
>> Id}".
>>
>> Is there a good way to detect the product id of the InstallShield
>> package beeing major upgraded so the registry key can be removed by
>> the WiX package?
>>
>> Thanks,
>> Magnus
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
>
>
>   ----------------------------------------------------------------------------------------------
> This E-mail is PLAIN text, not support HTML, see instruction below on how to report SPAM.
> -----------------------------------------------------------------------------------------------
> To submit spam as an attachment to an email message using a mail client:
> 1. Open a new email message.
> 2. Drag the spam email from the Inbox into the new email message.
> 3. Enter asa at websense.com in the To field.
> 4. Click Send.
> -----------------------------------------------------------------------------------------------