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 application off 
of the machine.Then you come by with your shiney new MSI, read in the 
configuration data ( if you have any ) and reinstall/reconfigure the 
application.
   
  This pattern prevents you from having 2 entries in Add/Remove Programs and 
all kinds of nasty reference count problems that would later manifest it self 
in a variety of ways including the inability to uninstall your shiney new MSI.

  Once your in this migrated state you can start using the upgrade servicing 
patterns that are built into MSI.
  
Anidil <[EMAIL PROTECTED]> wrote:
  
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 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 footprint of the old install off the machine.
> 
> Praveen Anidil wrote: How do i get the upgradecode
> for Non-MSI project?
> 
> On Jan 18, 2008 5:53 PM, Christopher Painter wrote:
> 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 wrote:
> 
> 
> 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
>> version
>> like '1.0.1', the one I'm working is "1.0.2".
>> Here is the Upgrade sequence in my wxs file:
>> 
>> 
>> > IncludeMaximum="no"/>
>> > IncludeMinimum="yes"/>
>> 
>> 
>> The Id attribute value of Upgrade tag is the same as the one displayed
>> within InstallShield UI's for the upgrade code of the package created
>> with 
>> it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php),
>> the PREVFOUND property should have attached the Product GUID during 
>> FindRelatedProducts action. While looking through the logs, nothing
>> appears to be found and no upgrade is performed. All that is logged
>> related to PREVFOUND is this: 
>> 
>> "SecureCustomProperties = NEWERFOUND;PREVFOUND" 
>> 
>> Any ideas?
>> 
>> Thx,
>> Dacian
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Sick sense of humor? Visit Yahoo! TV's 
>> Comedy with an Edge to see what's on, when. 
>> http://tv.yahoo.com/collections/222
>> -
>> This SF.net email is sponsored by DB2 Express 
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/ 
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p14948095.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list 
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users 
> 
> 
> 
> -
> Looking for last minute shopping deals? Find them fast with Yahoo!
> Search.
> 
> 
> 
> 
> -- 
> Regards
> Praveen Anidil 
> 
> 
> -
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it
> now.
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Upgrade-InstallShield-package-tp1095302

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 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 footprint of the old install off the machine.
> 
> Praveen Anidil <[EMAIL PROTECTED]> wrote:   How do i get the upgradecode
> for Non-MSI project?
> 
>   On Jan 18, 2008 5:53 PM, Christopher Painter <[EMAIL PROTECTED]> wrote:
> 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 PROTECTED]> wrote:
>   
> 
> 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
>> version
>> like '1.0.1', the one I'm working is "1.0.2".
>> Here is the Upgrade sequence in my wxs file:
>> 
>> 
>> > IncludeMaximum="no"/>
>> > IncludeMinimum="yes"/>
>> 
>> 
>> The Id attribute value of Upgrade tag is the same as the one displayed
>> within InstallShield UI's for the upgrade code of the package created
>> with 
>> it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php),
>> the PREVFOUND property should have attached the Product GUID during 
>> FindRelatedProducts action. While looking through the logs, nothing
>> appears to be found and no upgrade is performed. All that is logged
>> related to PREVFOUND is this: 
>> 
>> "SecureCustomProperties = NEWERFOUND;PREVFOUND" 
>> 
>> Any ideas?
>> 
>> Thx,
>> Dacian
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Sick sense of humor? Visit Yahoo! TV's 
>> Comedy with an Edge to see what's on, when. 
>> http://tv.yahoo.com/collections/222
>> -
>> This SF.net email is sponsored by DB2 Express 
>> Download DB2 Express C - the FREE version of DB2 express and take
>> control of your XML. No limits. Just data. Click to get it now.
>> http://sourceforge.net/powerbar/db2/ 
>> ___
>> WiX-users mailing list
>> WiX-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wix-users
>> 
>> 
> 
> -- 
> View this message in context:
> http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p14948095.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008. 
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list 
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users 
>   
>   
>   
> -
>   Looking for last minute shopping deals? Find them fast with Yahoo!
> Search.
> 
> 
> 
> 
> -- 
> Regards
> Praveen Anidil 
> 
>
> -
> Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it
> now.
> -
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p15016020.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 doesn't use Windows Installer,
then it won't have an UpgradeCode and Windows Installer won't know
about it or be able to upgrade it away.  You will have to use some
other mechanism to identify that version of the product and upgrade it
off the machine.

If it is MSI based, then the UpgradeCode is stored in the Property
table of the MSI.  Open the MSI in Orca and look at the Property table
to find the value for the UpgradeCode property.
-- 
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
  

Legalize Adulthood! 

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 footprint of the old 
install off the machine.

Praveen Anidil <[EMAIL PROTECTED]> wrote:   How do i get the upgradecode for 
Non-MSI project?

  On Jan 18, 2008 5:53 PM, Christopher Painter <[EMAIL PROTECTED]> wrote:
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 PROTECTED]> wrote:
  

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 version
> like '1.0.1', the one I'm working is "1.0.2".
> Here is the Upgrade sequence in my wxs file:
> 
> 
> > IncludeMaximum="no"/>
> > IncludeMinimum="yes"/>
> 
> 
> The Id attribute value of Upgrade tag is the same as the one displayed
> within InstallShield UI's for the upgrade code of the package created with 
> it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php),
> the PREVFOUND property should have attached the Product GUID during 
> FindRelatedProducts action. While looking through the logs, nothing
> appears to be found and no upgrade is performed. All that is logged
> related to PREVFOUND is this: 
> 
> "SecureCustomProperties = NEWERFOUND;PREVFOUND" 
> 
> Any ideas?
> 
> Thx,
> Dacian
> 
> 
> 
> 
> 
> 
> 
> 
> Sick sense of humor? Visit Yahoo! TV's 
> Comedy with an Edge to see what's on, when. 
> http://tv.yahoo.com/collections/222
> -
> This SF.net email is sponsored by DB2 Express 
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/ 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p14948095.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list 
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users 
  
  
  
-
  Looking for last minute shopping deals? Find them fast with Yahoo! Search.




-- 
Regards
Praveen Anidil 

   
-
Be a better friend, newshound, and know-it-all with Yahoo! Mobile.  Try it now.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 PROTECTED]> wrote:
  

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 version
> like '1.0.1', the one I'm working is "1.0.2".
> Here is the Upgrade sequence in my wxs file:
> 
> 
> > IncludeMaximum="no"/>
> > IncludeMinimum="yes"/>
> 
> 
> The Id attribute value of Upgrade tag is the same as the one displayed
> within InstallShield UI's for the upgrade code of the package created with
> it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php),
> the PREVFOUND property should have attached the Product GUID during
> FindRelatedProducts action. While looking through the logs, nothing
> appears to be found and no upgrade is performed. All that is logged
> related to PREVFOUND is this: 
> 
> "SecureCustomProperties = NEWERFOUND;PREVFOUND"
> 
> Any ideas?
> 
> Thx,
> Dacian
> 
> 
> 
> 
> 
> 
> 
> 
> Sick sense of humor? Visit Yahoo! TV's 
> Comedy with an Edge to see what's on, when. 
> http://tv.yahoo.com/collections/222
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p14948095.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


   
-
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 version
> like '1.0.1', the one I'm working is "1.0.2".
> Here is the Upgrade sequence in my wxs file:
> 
> 
>  IncludeMaximum="no"/>
>  IncludeMinimum="yes"/>
> 
> 
> The Id attribute value of Upgrade tag is the same as the one displayed
> within InstallShield UI's for the upgrade code of the package created with
> it. As far as I understand (http://www.tramontana.co.hu/wix/lesson4.php),
> the PREVFOUND property should have attached the Product GUID during
> FindRelatedProducts action. While looking through the logs, nothing
> appears to be found and no upgrade is performed. All that is logged
> related to PREVFOUND is this: 
> 
> "SecureCustomProperties = NEWERFOUND;PREVFOUND"
> 
> Any ideas?
> 
> Thx,
> Dacian
> 
> 
> 
> 
> 
> 
>
> 
> Sick sense of humor? Visit Yahoo! TV's 
> Comedy with an Edge to see what's on, when. 
> http://tv.yahoo.com/collections/222
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Upgrade-InstallShield-package-tp10953020p14948095.html
Sent from the wix-users mailing list archive at Nabble.com.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian 

Hi Phil,

This is what I did actually, I scheduled my RemoveExistsingProducts immediately 
after InstallInitialize instead of InstallFinalize like I had it before. Now, I 
have my files removed first then the new ones deployed correctly, which looks 
ok.

Thx for the help,
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 RemoveExistingProducts after InstallFinalize.  
Immediately after InstallInitialize is better if you expect a major upgrade to 
behave like an uninstall of the old product followed by an install of the new. 


Phil Wilson 




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. Looking with Orca 
throughout the Component table on the IS msi installation file, I saw some of 
the components don't have a KeyPath set (the KeyPath column is empty). The WiX 
source for my new version of the product has KeyPath set on the component 
containing the same file, like below:


   
   
   
   

   

   






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 from the IS deployement gets removed (the 
Component containing them isn't present in my new installation).
2. File1.exe 
and File2.exe from my new setup are deployed as they are new components to be 
installed by the upgrade.

At the end of the day, none File1.exe or 
File2.exe are present in the installation folder.

Am I doing something 
wrong here?

Dacian




- 
Original Message 
From: "Wilson, Phil" 
<[EMAIL PROTECTED]>
To: 
wix-users@lists.sourceforge.net
Sent: Monday, 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. 

Phil Wilson 

 




From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] 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 one I was using (displayed by IS UI). Now it looks 
like some upgrade is done (files are replaced and on uninstall they are removed 
from the system).

I have two questions though related to the upgrade 
process:

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 msi files I generated 
with WiX but have different versions. It just goes like a normal install, even 
if some components are upgraded. What I'd expect is getting an error when 
double 
click ("Another version..."), but when launched with REINSTALL=ALL 
REINSTALLMODE=vomus it should work.

2. At the end of the installation, I 
have two entries within Add/Remove Programs list: one with the previous name 
for 
the product and under it the new name for the product. There is just the Remove 
button for the previous product version (by design) and clicking on it just 
removes the entry from the Add/Remove list (without an installation or 
whatever). What I'd expect is no entry for the previous version in the 
list.

Any ideas why?


Thx,
Dacian



- 
Original Message 
From: "Wilson, Phil" 
<[EMAIL PROTECTED]>
To: 
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 on the right track.  
Versions are also another reason why a major upgrade won't detect an older one. 


Phil 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 your script displays "Context 4&quo

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread Wilson, Phil 
If you're really doing a major upgrade, this sounds like maybe you have
RemoveExistingProducts after InstallFinalize.  Immediately after
InstallInitialize is better if you expect a major upgrade to behave like
an uninstall of the old product followed by an install of the new. 

Phil Wilson 




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. Looking
with Orca throughout the Component table on the IS msi installation
file, I saw some of the components don't have a KeyPath set (the KeyPath
column is empty). The WiX source for my new version of the product has
KeyPath set on the component containing the same file, like below:


   
  
   
   
   






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 from the IS deployement gets removed (the
Component containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are
new components to be installed by the upgrade.

At the end of the day, none File1.exe or File2.exe are present in the
installation folder.

Am I doing something wrong here?

Dacian




- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Monday, 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. 

Phil Wilson 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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 one I was using (displayed by IS UI). Now it looks like some
upgrade is done (files are replaced and on uninstall they are removed
from the system).

I have two questions though related to the upgrade process:

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 msi
files I generated with WiX but have different versions. It just goes
like a normal install, even if some components are upgraded. What I'd
expect is getting an error when double click ("Another version..."), but
when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work.

2. At the end of the installation, I have two entries within Add/Remove
Programs list: one with the previous name for the product and under it
the new name for the product. There is just the Remove button for the
previous product version (by design) and clicking on it just removes the
entry from the Add/Remove list (without an installation or whatever).
What I'd expect is no entry for the previous version in the list.

Any ideas why?


Thx,
Dacian



- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: 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 on the right track.  Versions are also another reason
why a major upgrade won't detect an older one. 

Phil 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 your script displays "Context 4", so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there
is no detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by
your script next to the product name I'm interested is something like
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my

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 from the IS deployement gets removed (the 
Component containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are 
new components to be installed by the upgrade.


Check a verbose log. The InstallValidate action logs the install state, 
request, and action state of each feature and component.


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian 


Hi,

I ran into some extra problems with my InstallShield upgrade. Looking with Orca 
throughout the Component table on the IS msi installation file, I saw some of 
the components don't have a KeyPath set (the KeyPath column is empty). The WiX 
source for my new version of the product has KeyPath set on the component 
containing the same file, like below:













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 from the IS deployement gets removed (the Component 
containing them isn't present in my new installation).
2. File1.exe and File2.exe from my new setup are deployed as they are new 
components to be installed by the upgrade.

At the end of the day, none File1.exe or File2.exe are present in the 
installation folder.

Am I doing something wrong here?

Dacian



- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
Sent: Monday, 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. 

Phil Wilson 

 




From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] 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 one I was using (displayed by IS UI). Now it looks 
like some upgrade is done (files are replaced and on uninstall they are removed 
from the system).

I have two questions though related to the upgrade 
process:

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 msi files I generated 
with WiX but have different versions. It just goes like a normal install, even 
if some components are upgraded. What I'd expect is getting an error when 
double 
click ("Another version..."), but when launched with REINSTALL=ALL 
REINSTALLMODE=vomus it should work.

2. At the end of the installation, I 
have two entries within Add/Remove Programs list: one with the previous name 
for 
the product and under it the new name for the product. There is just the Remove 
button for the previous product version (by design) and clicking on it just 
removes the entry from the Add/Remove list (without an installation or 
whatever). What I'd expect is no entry for the previous version in the 
list.

Any ideas why?


Thx,
Dacian



- 
Original Message 
From: "Wilson, Phil" 
<[EMAIL PROTECTED]>
To: 
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 on the right track.  
Versions are also another reason why a major upgrade won't detect an older one. 


Phil 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 your script displays "Context 4", so there is a per-machine 
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no 
detection for the product IS created.

A strange thing I saw running your 
script: the product GUID displayed by your script next to the product name I'm 
interested is something like 
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product 
code displayed by IS within its UI 
is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think 
the UpgradeCode on which I base my  element to detect the 
previous version installed out there is wrong (I take it from the same IS UI 
which displays the "wrong" product code above). I don't see a property for 
retrieving the UpgradeCode within the WindowsInstaller automation interface in 
order 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
Su

Re: [WiX-users] Upgrade InstallShield package

2007-06-12 Thread fiordean dacian 

Hi Bob,

I just reviewed the REINSTALL/REINSTALLMODE which indeed is used for minor 
upgrades. My fault...

Thanks for the help,
Dacian



- Original Message 
From: Bob Arnson <[EMAIL PROTECTED]>
To: fiordean dacian <[EMAIL PROTECTED]>
Cc: wix-users@lists.sourceforge.net
Sent: 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 WiX code), but there is no message saying
"Another version of ..." like I get when I do an upgrade with two msi
files I generated with WiX but have different versions. It just goes
like a normal install, even if some components are upgraded. What I'd
expect is getting an error when double click ("Another version..."),
but when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work.

  

  




The REINSTALL/REINSTALLMODE behavior you describe is a minor upgrade.
The Upgrade/UpgradeVersion schema is used to declare a major upgrade,
which removes the previous product version as part of installing the
newer.



Which do you want?



-- 
sig://boB
http://joyofsetup.com/






   

Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for 
today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow  -
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 msi 
files I generated with WiX but have different versions. It just goes 
like a normal install, even if some components are upgraded. What I'd 
expect is getting an error when double click ("Another version..."), 
but when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work.


The REINSTALL/REINSTALLMODE behavior you describe is a minor upgrade. 
The Upgrade/UpgradeVersion schema is used to declare a major upgrade, 
which removes the previous product version as part of installing the newer.


Which do you want?

--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

2007-06-11 Thread Wilson, Phil 
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. 

Phil Wilson 

 



From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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 one I was using (displayed by IS UI). Now it looks like some
upgrade is done (files are replaced and on uninstall they are removed
from the system).

I have two questions though related to the upgrade process:

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 msi
files I generated with WiX but have different versions. It just goes
like a normal install, even if some components are upgraded. What I'd
expect is getting an error when double click ("Another version..."), but
when launched with REINSTALL=ALL REINSTALLMODE=vomus it should work.

2. At the end of the installation, I have two entries within Add/Remove
Programs list: one with the previous name for the product and under it
the new name for the product. There is just the Remove button for the
previous product version (by design) and clicking on it just removes the
entry from the Add/Remove list (without an installation or whatever).
What I'd expect is no entry for the previous version in the list.

Any ideas why?


Thx,
Dacian



- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: 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 on the right track.  Versions are also another reason
why a major upgrade won't detect an older one. 

Phil 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 your script displays "Context 4", so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there
is no detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by
your script next to the product name I'm interested is something like
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my 
element to detect the previous version installed out there is wrong (I
take it from the same IS UI which displays the "wrong" product code
above). I don't see a property for retrieving the UpgradeCode within the
WindowsInstaller automation interface in order 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 has a custom action (ISSetAllUsers) that sets ALLUSERS, so
looking in the raw MSI file won't tell you what's going on. It's mostly
used when it upgrades previous products, but nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install. 
 
This script might help. If it reports a context of 4 if the product is
installed per-machine, 2 if for a user and unmanaged. 
 
Option Explicit
Public installer, fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt,
sid, psorce, pcache, pvers
 
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("prodex.txt", True)
 
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on error resume next
For Each prod In installer.ProductsEx("", "", 7)
   pid = prod.ProductCode
   contxt = prod.Context
   sid=prod.usersid
   pname = prod.InstallProperty("InstalledProductName")
   psorce=prod.InstallProperty( "InstallSource")
   ploc =prod.InstallProperty( "InstallLocation")

Re: [WiX-users] Upgrade InstallShield package

2007-06-11 Thread fiordean dacian 

Hi,

I located and opened with Orca the cached msi file under Windows\Installer. The 
UpgradeCode is, of course, different compared with the one I was using 
(displayed by IS UI). Now it looks like some upgrade is done (files are 
replaced and on uninstall they are removed from the system).

I have two questions though related to the upgrade process:

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 msi files I generated with WiX 
but have different versions. It just goes like a normal install, even if some 
components are upgraded. What I'd expect is getting an error when double click 
("Another version..."), but when launched with REINSTALL=ALL 
REINSTALLMODE=vomus it should work.

2. At the end of the installation, I have two entries within Add/Remove 
Programs list: one with the previous name for the product and under it the new 
name for the product. There is just the Remove button for the previous product 
version (by design) and clicking on it just removes the entry from the 
Add/Remove list (without an installation or whatever). What I'd expect is no 
entry for the previous version in the list.

Any ideas why?


Thx,
Dacian


- Original Message 
From: "Wilson, Phil" <[EMAIL PROTECTED]>
To: 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 on the right track.  
Versions are also another reason why a major upgrade won't detect an older one. 


Phil 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 your script displays "Context 4", so there is a per-machine 
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no 
detection for the product IS created.

A strange thing I saw running your 
script: the product GUID displayed by your script next to the product name I'm 
interested is something like 
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product 
code displayed by IS within its UI 
is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think 
the UpgradeCode on which I base my  element to detect the 
previous version installed out there is wrong (I take it from the same IS UI 
which displays the "wrong" product code above). I don't see a property for 
retrieving the UpgradeCode within the WindowsInstaller automation interface in 
order 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 has a custom action (ISSetAllUsers) that 
sets ALLUSERS, so looking in the raw MSI file won't tell you 
what's going on. It's mostly used when it upgrades previous products, but 
nevertheless I recommend 
looking at a log to see what's actually happening to the ALLUSERS value 
during the InstallShield MSI install. 

 

This script might help. If it reports a 
context of 4 if the product is installed per-machine, 2 if for a user and 
unmanaged. 

 

Option Explicit
Public installer, 
fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache, 
pvers

 

Set fso = 
CreateObject("Scripting.FileSystemObject")
Set a = 
fso.CreateTextFile("prodex.txt", True)

 

' Connect to Windows Installer 
object
Set installer = 
CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on 
error resume next
For Each prod In installer.ProductsEx("", "", 
7)
   pid = prod.ProductCode
   contxt = 
prod.Context
   sid=prod.usersid
   pname = 
prod.InstallProperty("InstalledProductName")
   
psorce=prod.InstallProperty( "InstallSource")
   ploc 
=prod.InstallProperty( "InstallLocation")  
   pcache = 
prod.InstallProperty("LocalPackage") 
  
pvers=prod.InstallProperty("VersionString")
   a.writeline (pid 
& " " & pname & " " & pvers & " installed at <" & 
ploc & "> from " & psorce & " Context " & 
contxt)
Next


Phil Wilson 



From: [EMAIL PROTECTED] 
[mailto:[EMAIL PROTECTED] On Behalf Of fiordean

Re: [WiX-users] Upgrade InstallShield package

2007-06-08 Thread Wilson, Phil 
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 on the right track.  Versions are also another reason
why a major upgrade won't detect an older one. 

Phil 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 your script displays "Context 4", so there is a per-machine
install done by IS. I have ALLUSERS set to 1 in my WiX source, but there
is no detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by
your script next to the product name I'm interested is something like
this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my 
element to detect the previous version installed out there is wrong (I
take it from the same IS UI which displays the "wrong" product code
above). I don't see a property for retrieving the UpgradeCode within the
WindowsInstaller automation interface in order 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 has a custom action (ISSetAllUsers) that sets ALLUSERS, so
looking in the raw MSI file won't tell you what's going on. It's mostly
used when it upgrades previous products, but nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install. 
 
This script might help. If it reports a context of 4 if the product is
installed per-machine, 2 if for a user and unmanaged. 
 
Option Explicit
Public installer, fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt,
sid, psorce, pcache, pvers
 
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("prodex.txt", True)
 
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on error resume next
For Each prod In installer.ProductsEx("", "", 7)
   pid = prod.ProductCode
   contxt = prod.Context
   sid=prod.usersid
   pname = prod.InstallProperty("InstalledProductName")
   psorce=prod.InstallProperty( "InstallSource")
   ploc =prod.InstallProperty( "InstallLocation")  
   pcache = prod.InstallProperty("LocalPackage") 
  pvers=prod.InstallProperty("VersionString")
   a.writeline (pid & " " & pname & " " & pvers & " installed at <" &
ploc & "> from " & 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 InstallShield package



Hi Bob,

ALLUSERS property is not set within the .msi file InstallShield
generates, which means there was a per-user installation (there is
something like ApplicationUsers property with the value ALLUSERS). My
.msi uses ALLUSERS with a value of 1 (so per-machine install). I removed
ALLUSERS property from my .msi.

Also, I switched for a major upgrade now (updated Product & UpgradeCode
GUIDs and Version), here is the Upgrade sequence:








The first Upgrade refers to previous InstallShield package out there,
second is for current version.

Well, I had no success yet.

Dacian




- 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 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 GUIDs and IDs the same, you need to do a major
upgrade to get to a "clean slate" install.



On top of that, it still doesn't look like the previous
installation was detected (the PREVFOUND property doesn't have a GUID
attached to it and no upgarde is proposed, just normal install).

Re: [WiX-users] Upgrade InstallShield package

2007-06-08 Thread fiordean dacian 

Hi Phil,

Looking through IS log I see ALLUSERS with a value of 1.

Running your script displays "Context 4", so there is a per-machine install 
done by IS. I have ALLUSERS set to 1 in my WiX source, but there is no 
detection for the product IS created.

A strange thing I saw running your script: the product GUID displayed by your 
script next to the product name I'm interested is something like this:

{B607D95A-A73C-444B-87BA-B4E9DBAC4DEE}

while the product code displayed by IS within its UI is:

{F1872E85-C933-44D4-8B88-85D68DD9B103}

which makes me think the UpgradeCode on which I base my  element to 
detect the previous version installed out there is wrong (I take it from the 
same IS UI which displays the "wrong" product code above). I don't see a 
property for retrieving the UpgradeCode within the WindowsInstaller automation 
interface in order 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 has a custom action (ISSetAllUsers) that 
sets ALLUSERS, so looking in the raw MSI file won't tell you 
what's going on. It's mostly used when it upgrades previous products, but 
nevertheless I recommend 
looking at a log to see what's actually happening to the ALLUSERS value 
during the InstallShield MSI install. 

 

This script might help. If it reports a 
context of 4 if the product is installed per-machine, 2 if for a user and 
unmanaged. 

 

Option Explicit
Public installer, 
fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt, sid, psorce, pcache, 
pvers

 

Set fso = 
CreateObject("Scripting.FileSystemObject")
Set a = 
fso.CreateTextFile("prodex.txt", True)

 

' Connect to Windows Installer 
object
Set installer = 
CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on 
error resume next
For Each prod In installer.ProductsEx("", "", 
7)
   pid = prod.ProductCode
   contxt = 
prod.Context
   sid=prod.usersid
   pname = 
prod.InstallProperty("InstalledProductName")
   
psorce=prod.InstallProperty( "InstallSource")
   ploc 
=prod.InstallProperty( "InstallLocation")  
   pcache = 
prod.InstallProperty("LocalPackage") 
  
pvers=prod.InstallProperty("VersionString")
   a.writeline (pid 
& " " & pname & " " & pvers & " installed at <" & 
ploc & "> from " & 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 
InstallShield package







Hi 
Bob,

ALLUSERS property is not set within the .msi file InstallShield 
generates, which means there was a per-user installation (there is something 
like ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS 
with a value of 1 (so per-machine install). I removed ALLUSERS property from my 
.msi.

Also, I switched for a major upgrade now (updated Product & 
UpgradeCode GUIDs and Version), here is the Upgrade sequence:










The first Upgrade refers to 
previous InstallShield package out there, second is for current 
version.

Well, I had no success yet.

Dacian




- 
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 
  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 GUIDs and IDs 
the same, you need to do a major upgrade to get to a "clean slate" 
install.



  
  On 
  top of that, it still doesn't look like the previous installation was 
detected 
  (the PREVFOUND property doesn't have a GUID attached to it and no upgarde is 
  proposed, just normal install).



The most common 
reason is that you're trying to mix and match values of ALLUSERS. MSI doesn't 
support a per-user install upgrading a per-machine install (or vice versa).
-- 
sig://boB
http://joyofsetup.com/






Sick sense of humor? Visit Yahoo! TV's Comedy 
with an Edge to see what's on, when. 
-
This SF.net email

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread Wilson, Phil 
InstallShield has a custom action (ISSetAllUsers) that sets ALLUSERS, so
looking in the raw MSI file won't tell you what's going on. It's mostly
used when it upgrades previous products, but nevertheless I recommend
looking at a log to see what's actually happening to the ALLUSERS value
during the InstallShield MSI install. 
 
This script might help. If it reports a context of 4 if the product is
installed per-machine, 2 if for a user and unmanaged. 
 
Option Explicit
Public installer, fullmsg, comp, prod, a, fso, pname, ploc, pid,contxt,
sid, psorce, pcache, pvers
 
Set fso = CreateObject("Scripting.FileSystemObject")
Set a = fso.CreateTextFile("prodex.txt", True)
 
' Connect to Windows Installer object
Set installer = CreateObject("WindowsInstaller.Installer")
a.writeline ("Products")
'on error resume next
For Each prod In installer.ProductsEx("", "", 7)
   pid = prod.ProductCode
   contxt = prod.Context
   sid=prod.usersid
   pname = prod.InstallProperty("InstalledProductName")
   psorce=prod.InstallProperty( "InstallSource")
   ploc =prod.InstallProperty( "InstallLocation")  
   pcache = prod.InstallProperty("LocalPackage") 
  pvers=prod.InstallProperty("VersionString")
   a.writeline (pid & " " & pname & " " & pvers & " installed at <" &
ploc & "> from " & 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 InstallShield package



Hi Bob,

ALLUSERS property is not set within the .msi file InstallShield
generates, which means there was a per-user installation (there is
something like ApplicationUsers property with the value ALLUSERS). My
.msi uses ALLUSERS with a value of 1 (so per-machine install). I removed
ALLUSERS property from my .msi.

Also, I switched for a major upgrade now (updated Product & UpgradeCode
GUIDs and Version), here is the Upgrade sequence:








The first Upgrade refers to previous InstallShield package out there,
second is for current version.

Well, I had no success yet.

Dacian




- 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 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 GUIDs and IDs the same, you need to do a major
upgrade to get to a "clean slate" install.



On top of that, it still doesn't look like the previous
installation was detected (the PREVFOUND property doesn't have a GUID
attached to it and no upgarde is proposed, just normal install).



The most common reason is that you're trying to mix and match values of
ALLUSERS. MSI doesn't support a per-user install upgrading a per-machine
install (or vice versa).

-- 
sig://boB
http://joyofsetup.com/




Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge
<http://us.rd.yahoo.com/evt=47093/*http://tv.yahoo.com/collections/222>
to see what's on, when. 
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread fiordean dacian 

Hi Bob,

ALLUSERS property is not set within the .msi file InstallShield generates, 
which means there was a per-user installation (there is something like 
ApplicationUsers property with the value ALLUSERS). My .msi uses ALLUSERS with 
a value of 1 (so per-machine install). I removed ALLUSERS property from my .msi.

Also, I switched for a major upgrade now (updated Product & UpgradeCode GUIDs 
and Version), here is the Upgrade sequence:








The first Upgrade refers to previous InstallShield package out there, second is 
for current version.

Well, I had no success yet.

Dacian



- 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
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 GUIDs and IDs the same, you need to do a major
upgrade to get to a "clean slate" install.




  
  On
top of that, it still doesn't look like the previous installation was
detected (the PREVFOUND property doesn't have a GUID attached to it and
no upgarde is proposed, just normal install).

  

  




The most common reason is that you're trying to mix and match values of
ALLUSERS. MSI doesn't support a per-user install upgrading a
per-machine install (or vice versa).

-- 
sig://boB
http://joyofsetup.com/






 

Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 GUIDs and IDs the same, you need to do a major 
upgrade to get to a "clean slate" install.


On top of that, it still doesn't look like the previous installation 
was detected (the PREVFOUND property doesn't have a GUID attached to 
it and no upgarde is proposed, just normal install).


The most common reason is that you're trying to mix and match values of 
ALLUSERS. MSI doesn't support a per-user install upgrading a per-machine 
install (or vice versa).


--
sig://boB
http://joyofsetup.com/

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrade InstallShield package

2007-06-05 Thread fiordean dacian 
Hi Rob,

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.

On top of that, it still doesn't look like the previous installation was 
detected (the PREVFOUND property doesn't have a GUID attached to it and no 
upgarde is proposed, just normal install).

Thx,
Dacian


- Original Message 
From: Rob Hamflett <[EMAIL PROTECTED]>
To: wix-users@lists.sourceforge.net
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 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:
> 
> 
>  Maximum="1.0.2" IncludeMaximum="no"/>
>  Minimum="1.0.2" IncludeMinimum="yes"/>
> 
> 
> The Id attribute value of Upgrade tag is the same as the one displayed 
> within InstallShield UI's for the upgrade code of the package created 
> with it. As far as I understand 
> (http://www.tramontana.co.hu/wix/lesson4.php), the PREVFOUND property 
> should have attached the Product GUID during FindRelatedProducts action. 
> While looking through the logs, nothing appears to be found and no 
> upgrade is performed. All that is logged related to PREVFOUND is this:
> 
> "SecureCustomProperties = NEWERFOUND;PREVFOUND"
> 
> Any ideas?
> 
> Thx,
> Dacian
> 
> 
> 
> 
> Luggage? GPS? Comic books?
> Check out fitting gifts for grads 
> <http://us.rd.yahoo.com/evt=48249/*http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz>
>  
> at Yahoo! Search.
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users







 

Don't get soaked.  Take a quick peak at the forecast
with the Yahoo! Search weather shortcut.
http://tools.search.yahoo.com/shortcuts/#loc_weather-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

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 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:
> 
> 
>  Maximum="1.0.2" IncludeMaximum="no"/>
>  Minimum="1.0.2" IncludeMinimum="yes"/>
> 
> 
> The Id attribute value of Upgrade tag is the same as the one displayed 
> within InstallShield UI's for the upgrade code of the package created 
> with it. As far as I understand 
> (http://www.tramontana.co.hu/wix/lesson4.php), the PREVFOUND property 
> should have attached the Product GUID during FindRelatedProducts action. 
> While looking through the logs, nothing appears to be found and no 
> upgrade is performed. All that is logged related to PREVFOUND is this:
> 
> "SecureCustomProperties = NEWERFOUND;PREVFOUND"
> 
> Any ideas?
> 
> Thx,
> Dacian
> 
> 
> 
> 
> Luggage? GPS? Comic books?
> Check out fitting gifts for grads 
> 
>  
> at Yahoo! Search.
> 
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> 
> 
> 
> 
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

[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 is the same as the one displayed within 
InstallShield UI's for the upgrade code of the package created with it. As far 
as I understand (http://www.tramontana.co.hu/wix/lesson4.php), the PREVFOUND 
property should have attached the Product GUID during FindRelatedProducts 
action. While looking through the logs, nothing appears to be found and no 
upgrade is performed. All that is logged related to PREVFOUND is this: 

"SecureCustomProperties = NEWERFOUND;PREVFOUND"

Any ideas?

Thx,
Dacian






   

Sick sense of humor? Visit Yahoo! TV's 
Comedy with an Edge to see what's on, when. 
http://tv.yahoo.com/collections/222-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users