Re: [WiX-users] Upgrade InstallShield package

2008-01-22 Thread Christopher Painter
I saw this scenario all the time in enterprise repackaging. You have to write a `forced uninstall` pattern. This is basically a clean up utility that harvests configuration data that you want to preserve, writes it somewhere for the new install to use and then programatically wipes the old ap

Re: [WiX-users] Upgrade InstallShield package

2008-01-22 Thread Anidil
Unfortunately there is no working silent uninstall routine with the legacy install..Can't i ever upgrade in this situation? Christopher Painter wrote: > > UpgradeCode is an MSI concept. A non-MSI project doesn't have an > UpgradeCode. In these cases you either hope that the legacy install ha

Re: [WiX-users] Upgrade InstallShield package

2008-01-18 Thread Richard
In article <[EMAIL PROTECTED]>, Anidil <[EMAIL PROTECTED]> writes: > Where can i find the upgrade code used by installshield? i couldn't locate > any GUID inside the installshied script The UpgradeCode is a Windows Installer mechanism. If the version of the product you're trying to upgrade

Re: [WiX-users] Upgrade InstallShield package

2008-01-18 Thread Christopher Painter
UpgradeCode is an MSI concept. A non-MSI project doesn't have an UpgradeCode. In these cases you either hope that the legacy install has a working silent uninstall routine that you can call via custom action or you have to write a custom action ( `forced uninstall pattern ) to wipe the footpri

Re: [WiX-users] Upgrade InstallShield package

2008-01-18 Thread Christopher Painter
InstallShield has MSI and Non-MSI project types. If it's an MSI project ( Basic MSI or InstallScript MSI ) then you'll find it in the Property table ( UpgradeCode Property). If the project was setup to support Major Upgrades you'll also find it in the Upgrade table. Anidil <[EMAIL PROTECT

Re: [WiX-users] Upgrade InstallShield package

2008-01-18 Thread Anidil
Where can i find the upgrade code used by installshield? i couldn't locate any GUID inside the installshied script fiordean dacian wrote: > > Hi, > > I have a package build with InstallShield deployed out there I'd like to > upgrade using an msi authored with WiX. The deployed package has a

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian
- Original Message From: "Wilson, Phil" <[EMAIL PROTECTED]> To: wix-users@lists.sourceforge.net Sent: Tuesday, June 12, 2007 6:26:05 PM Subject: Re: [WiX-users] Upgrade InstallShield package If you're really doing a major upgrade, this sounds like maybe you have RemoveE

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread Wilson, Phil
ilson From: fiordean dacian [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 12, 2007 7:09 AM To: Wilson, Phil; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade InstallShield package Hi, I ran into some extra problems with my InstallShield upgrade. Lo

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread Bob Arnson
fiordean dacian wrote: Now the problem is IS component I want to upgrade contained, when the setup was built, both File1 and File2, without a KeyPath. What I tried is I used new GUIDs for both Component1 and Component2 in my new WiX source. What I was expecting is: 1. File1.exe and File2.exe

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian
onday, June 11, 2007 11:33:04 PM Subject: Re: [WiX-users] Upgrade InstallShield package 1. Is because this is a major upgrade and your new product has a different ProductCode guid. 2. Is probably because you've set "OnlyDetect" if I recall the syntax correctly. P

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian
ent: Tuesday, June 12, 2007 8:06:26 AM Subject: Re: [WiX-users] Upgrade InstallShield package fiordean dacian wrote: 1. When double click on my new msi, it detects there is a previous product installed (there is a PREVFOUND property set I provided within the Upgrade sequence of my Wi

Re: [WiX-users] Upgrade InstallShield package

2007-06-11 Thread Bob Arnson
fiordean dacian wrote: 1. When double click on my new msi, it detects there is a previous product installed (there is a PREVFOUND property set I provided within the Upgrade sequence of my WiX code), but there is no message saying "Another version of ..." like I get when I do an upgrade with two

Re: [WiX-users] Upgrade InstallShield package

2007-06-11 Thread Wilson, Phil
D] On Behalf Of fiordean dacian Sent: Monday, June 11, 2007 8:14 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade InstallShield package Hi, I located and opened with Orca the cached msi file under Windows\Installer. The UpgradeCode is, of course, different compared with the

Re: [WiX-users] Upgrade InstallShield package

2007-06-11 Thread fiordean dacian
: wix-users@lists.sourceforge.net Sent: Friday, June 8, 2007 8:36:03 PM Subject: Re: [WiX-users] Upgrade InstallShield package If you can locate the cached MSI file in Windows\installer, opening it with Orca will show the UpgradeCode in the Property table. That might help see if you'

Re: [WiX-users] Upgrade InstallShield package

2007-06-08 Thread Wilson, Phil
hil Wilson From: fiordean dacian [mailto:[EMAIL PROTECTED] Sent: Friday, June 08, 2007 10:00 AM To: Wilson, Phil; wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade InstallShield package Hi Phil, Looking through IS log I see ALLUSERS with a value of 1. Running y

Re: [WiX-users] Upgrade InstallShield package

2007-06-08 Thread fiordean dacian
to check if the UpgradeCode IS installed product has. Dacian - Original Message From: "Wilson, Phil" <[EMAIL PROTECTED]> To: wix-users@lists.sourceforge.net Sent: Tuesday, June 5, 2007 7:22:22 PM Subject: Re: [WiX-users] Upgrade InstallShield package InstallShield

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread Wilson, Phil
p; psorce & " Context " & contxt) Next Phil Wilson From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of fiordean dacian Sent: Tuesday, June 05, 2007 9:46 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Upgrade InstallS

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread fiordean dacian
cian - Original Message From: Bob Arnson <[EMAIL PROTECTED]> To: fiordean dacian <[EMAIL PROTECTED]> Cc: wix-users@lists.sourceforge.net Sent: Tuesday, June 5, 2007 5:23:07 PM Subject: Re: [WiX-users] Upgrade InstallShield package fiordean dacian wrote: That

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread Bob Arnson
fiordean dacian wrote: That would remove my previous installation, right? I'm not sure I want that since the user might have configured the product (registry keys, config files, etc.) and I don't want that to be removed. I just want an upgrade of what's out there. Unless you kept all your GUI

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread fiordean dacian
Sent: Tuesday, June 5, 2007 10:36:43 AM Subject: Re: [WiX-users] Upgrade InstallShield package You want to remove OnlyDetect from the check for a previous version, and make sure you have RemoveExistingProducts scheduled. Rob fiordean dacian wrote: > Hi, > > I have a package build w

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread Rob Hamflett
You want to remove OnlyDetect from the check for a previous version, and make sure you have RemoveExistingProducts scheduled. Rob fiordean dacian wrote: > Hi, > > I have a package build with InstallShield deployed out there I'd like to > upgrade using an msi authored with WiX. The deployed pa

[WiX-users] Upgrade InstallShield package

2007-06-04 Thread fiordean dacian
Hi, I have a package build with InstallShield deployed out there I'd like to upgrade using an msi authored with WiX. The deployed package has a version like '1.0.1', the one I'm working is "1.0.2". Here is the Upgrade sequence in my wxs file: The Id attribute value of Upgrade tag i