subject:"Re\: \[WiX\-users\] Upgrades"

Re: [WiX-users] Upgrades

2013-12-01 Thread Blair Murri

When Burn installs a newer MSI that MSI should still generally remove older 
versions of itself (#1 reason: your customers may not do what you expect).
 
Having said that, if an MSI does what is expected, then the older MSI will be 
removed as part of its upgrade. When the older bundle is then removed, it will 
find that the MSI it had installed is no longer installed, and it will remove 
its cache of that MSI as it removes itself, thus completing its cleanup.
 
Does that make more sense? (I didn't search the older parts of this 
conversation, so there may be something I'm missing...)
 
> Date: Thu, 28 Nov 2013 13:39:39 -0500
> From: michael.ogil...@pixelink.com
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrades
> 
> Hello Phil,
> 
> Thanks for the info.
> 
> >From the log files it looks like it uninstalls the stuff twice.
> 
> >From the install logs of the MSI it goes through the uninstall then the
> install then it looks like Burn also uninstalls the old version.
> 
> just does not make sense.
> 
> Thank you,
> Michael Ogilvie
> 
> 
> 
> -Original Message-
> From: Phill Hogland [mailto:phogl...@rimage.com] 
> Sent: Wednesday, November 27, 2013 10:54 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Upgrades
> 
> Generally yes, although you might not specify all of those attributes.
> Each
> MSI needs some information instructing it how to process upgrades, which
> is
> independent of how the MSI is launched, as part of a bundle chain or
> directly.
> 
> 
> 
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-t
> p7590978p7590984.html
> Sent from the wix-users mailing list archive at Nabble.com.
> 
> 
> --
> Rapidly troubleshoot problems before they affect your business. Most IT 
> organizations don't have a clear picture of how application performance 
> affects their revenue. With AppDynamics, you get 100% visibility into
> your 
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
> AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clk
> trk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> 
> --
> Rapidly troubleshoot problems before they affect your business. Most IT 
> organizations don't have a clear picture of how application performance 
> affects their revenue. With AppDynamics, you get 100% visibility into your 
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
  
--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades

2013-11-28 Thread Michael Ogilvie

Hello Phil,

Thanks for the info.

>From the log files it looks like it uninstalls the stuff twice.

>From the install logs of the MSI it goes through the uninstall then the
install then it looks like Burn also uninstalls the old version.

just does not make sense.

Thank you,
Michael Ogilvie



-Original Message-
From: Phill Hogland [mailto:phogl...@rimage.com] 
Sent: Wednesday, November 27, 2013 10:54 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Upgrades

Generally yes, although you might not specify all of those attributes.
Each
MSI needs some information instructing it how to process upgrades, which
is
independent of how the MSI is launched, as part of a bundle chain or
directly.



--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-t
p7590978p7590984.html
Sent from the wix-users mailing list archive at Nabble.com.


--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into
your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of
AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clk
trk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades

2013-11-27 Thread Phill Hogland

Generally yes, although you might not specify all of those attributes.  Each
MSI needs some information instructing it how to process upgrades, which is
independent of how the MSI is launched, as part of a bundle chain or
directly.



--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-tp7590978p7590984.html
Sent from the wix-users mailing list archive at Nabble.com.

--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades...

2013-04-02 Thread StevenOgilvie

Thanks Rob Thought so...
  
Steve Ogilvie   “Our lives begin to end the day we become silent about 
things that matter.”, Dr. Martin Luther King Jr. Sent from my BlackBerry 10 
smartphone. 

From: 
robmen [via Windows Installer XML (WiX) toolset] Sent: Tuesday, April 2, 2013 
09:33 PM To: StevenOgilvie Subject: Re: Upgrades... 

That's just setting a bunch of properties. If you don't use the 
properties,
you don't need all that. MajorUpgrade element is all you need (plus change
Product/@Id and do not change Product/@UpgradeCode).
On Tue, Apr 2, 2013 at 6:01 AM, StevenOgilvie < [hidden email] > wrote:
> Hi folks,
>
> I have a few installers that I am writing in WIX 3.7
>
> I was just using:
>
>  DowngradeErrorMessage="A newer version of $(var.PlatformProductName) is
> already installed. Setup will now exit." />
>
> To handle upgrades (uninstall older version, install new version)
>
> I saw a blog on upgrades and they recommended doing the below, my question
> is, do I need to add all that??
>
>
>
>
>    Schedule="afterInstallInitialize" AllowDowngrades="no"/>
>      Value="true">
>       NOT Installed AND NOT WIX_UPGRADE_DETECTED AND NOT
> WIX_DOWNGRADE_DETECTED
>       
>     
>       WIX_UPGRADE_DETECTED AND NOT (REMOVE="ALL")
>       
>      Sequence="execute" Value="true">
>       (REMOVE="ALL") AND UPGRADINGPRODUCTCODE
>       
>     
>       Installed AND (REMOVE="ALL") AND NOT 
(WIX_UPGRADE_DETECTED OR
> UPGRADINGPRODUCTCODE)
>       
>     
>       Installed AND NOT Upgrading AND NOT Uninstalling AND 
NOT
> UPGRADINGPRODUCTCODE
>       
>
> 
>       
>       
>       
>
> 
>       
>       
>
> Thanks,
>
> steve
>
>
>
>
> --
> View this message in context:
> 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-tp7584816.html
 > Sent from the wix-users mailing list archive at Nabble.com.
>
>
> 
--
> Own the Future-Intel(R) Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest. Compete
> for recognition, cash, and the chance to get your game on Steam.
> $5K grand prize plus 10 genre and skill prizes. Submit your demo
> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 > 
___
> WiX-users mailing list
> [hidden email] 
> https://lists.sourceforge.net/lists/listinfo/wix-users >
>
--
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 
___
WiX-users mailing list
[hidden email] 
https://lists.sourceforge.net/lists/listinfo/wix-users 








If you reply to this email, your message will be added to the 
discussion below: 

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-tp7584816p7584818.html
 



To unsubscribe from Upgrades..., click here . 
NAML 
 




--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-tp7584816p7584819.html
Sent from the wix-users mailing list archive at Nabble.com.
--
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, c

Re: [WiX-users] Upgrades...

2013-04-02 Thread Rob Mensching

That's just setting a bunch of properties. If you don't use the properties,
you don't need all that. MajorUpgrade element is all you need (plus change
Product/@Id and do not change Product/@UpgradeCode).


On Tue, Apr 2, 2013 at 6:01 AM, StevenOgilvie  wrote:

> Hi folks,
>
> I have a few installers that I am writing in WIX 3.7
>
> I was just using:
>
>  DowngradeErrorMessage="A newer version of $(var.PlatformProductName) is
> already installed. Setup will now exit." />
>
> To handle upgrades (uninstall older version, install new version)
>
> I saw a blog on upgrades and they recommended doing the below, my question
> is, do I need to add all that??
>
>
>
>
>Schedule="afterInstallInitialize" AllowDowngrades="no"/>
>  Value="true">
>   NOT Installed AND NOT WIX_UPGRADE_DETECTED AND NOT
> WIX_DOWNGRADE_DETECTED
>   
> 
>   WIX_UPGRADE_DETECTED AND NOT (REMOVE="ALL")
>   
>  Sequence="execute" Value="true">
>   (REMOVE="ALL") AND UPGRADINGPRODUCTCODE
>   
> 
>   Installed AND (REMOVE="ALL") AND NOT (WIX_UPGRADE_DETECTED OR
> UPGRADINGPRODUCTCODE)
>   
> 
>   Installed AND NOT Upgrading AND NOT Uninstalling AND NOT
> UPGRADINGPRODUCTCODE
>   
>
> 
>   
>   
>   
>
> 
>   
>   
>
> Thanks,
>
> steve
>
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-tp7584816.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> --
> Own the Future-Intel(R) Level Up Game Demo Contest 2013
> Rise to greatness in Intel's independent game demo contest. Compete
> for recognition, cash, and the chance to get your game on Steam.
> $5K grand prize plus 10 genre and skill prizes. Submit your demo
> by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
> ___
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete 
for recognition, cash, and the chance to get your game on Steam. 
$5K grand prize plus 10 genre and skill prizes. Submit your demo 
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

Sorry used to InstallShield and other Front ends to MSI handling upgrades..

I like the MajorUpgrade one line of code instead of a dozen...

Thanks Neil

STeve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: December-20-12 5:13 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Not sure what you mean by extra code, this is what an upgrade looks like. Using 
afterInstallValidate will uninstall and then install, using afterInstallExecute 
will replace files (not a good explanation but see here for a real description 
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ and 
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ )

Neil 

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 21:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Cool it worked... I don't like the fact that you need to do "extra" code to 
make it look like an upgrade, it looks like a regular install except during the 
progress it is uninstalling the previous version then installing the new one...

I did what you suggested down below :) less code for sure :)

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 


So that would give something like this:
  



That authoring should be simpler to debug.

Neil


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:






 
  
   

Where:  in an include file I include in 
my product.wxs 
  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Neil Sleightholm

Not sure what you mean by extra code, this is what an upgrade looks like. Using 
afterInstallValidate will uninstall and then install, using afterInstallExecute 
will replace files (not a good explanation but see here for a real description 
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/ and 
http://www.joyofsetup.com/2010/01/16/major-upgrades-now-easier-than-ever/ )

Neil 

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 20 December 2012 21:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Cool it worked... I don't like the fact that you need to do "extra" code to 
make it look like an upgrade, it looks like a regular install except during the 
progress it is uninstalling the previous version then installing the new one...

I did what you suggested down below :) less code for sure :)

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 


So that would give something like this:
  



That authoring should be simpler to debug.

Neil


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:






 
  
   

Where:  in an include file I include in 
my product.wxs 
  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-a

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Neil Sleightholm

I am not sure why you would need this, it is not something I have needed.

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 20 December 2012 21:39
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

What about the

  CA: Setting REINSTALLMODE to 
amus...

Is that required?

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 

So that would give something like this:

That authoring should be simpler to debug.

Neil

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:

Where:  in an include file I include in 
my product.wxs 

  NOT NEWERVERSIONDETECTED

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...

then:

where 
I have the following defined:

and have a productcode and upgradecode that I don't change...

customactions:

  CA: Setting REINSTALLMODE to 
amus...

  CA: Setting up 
NEWAPPFOUND...

  NEWAPPFOUND

  NOT NEWERVERSIONDETECTED

  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-ad

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

Cool it worked... I don't like the fact that you need to do "extra" code to 
make it look like an upgrade, it looks like a regular install except during the 
progress it is uninstalling the previous version then installing the new one...

I did what you suggested down below :) less code for sure :)

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 


So that would give something like this:
  



That authoring should be simpler to debug.

Neil


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:






 
  
   

Where:  in an include file I include in 
my product.wxs 
  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logm

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

What about the 


  CA: Setting REINSTALLMODE to 
amus...


Is that required?

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: December-20-12 4:08 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 


So that would give something like this:
  



That authoring should be simpler to debug.

Neil


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:






 
  
   

Where:  in an include file I include in 
my product.wxs 
  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

-

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Neil Sleightholm

Correction - use  it will be 
simpler.

-Original Message-
From: Neil Sleightholm 
Sent: 20 December 2012 21:06
To: General discussion for Windows Installer XML toolset.
Subject: RE: [WiX-users] Upgrades NOT working on a new install

Use 
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 

So that would give something like this:

That authoring should be simpler to debug.

Neil

-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:

Where:  in an include file I include in 
my product.wxs 

  NOT NEWERVERSIONDETECTED

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...

then:

where 
I have the following defined:

and have a productcode and upgradecode that I don't change...

customactions:

  CA: Setting REINSTALLMODE to 
amus...

  CA: Setting up 
NEWAPPFOUND...

  NEWAPPFOUND

  NOT NEWERVERSIONDETECTED

  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve

--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
__

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Neil Sleightholm

Use 
- Product/@Id="*"
- Remove the Id from Package completely
- I would revert to the MajorUpgrade element and delete all the Upgrade 
elements and RemoveExistingProducts,  FindRelatedProducts and 


So that would give something like this:
  



That authoring should be simpler to debug.

Neil


-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com] 
Sent: 20 December 2012 19:26
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

Okay,

I now have:






 
  
   

Where:  in an include file I include in 
my product.wxs 
  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Resc

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread John Ludlow

An upgrade would look like a fresh install unless you've specifically
authored UI to handle upgrades. How many entries for your application
are there in the Programs and Features panel?  If there's 2, then you
know you have a problem.

On 20 December 2012 20:30, Steven Ogilvie  wrote:
> No I only change the ProductVersion to a higher number (minor.build) and that 
> was it
>
> -Original Message-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: December-20-12 3:27 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>
> What do you mean by "When I run the second it's like the first one was not 
> installed, it was like running a fresh install"? Does the verbose log tell 
> you whether 4.0.1.25 was detected and uninstalled? I guess I should also ask 
> the obvious question, did you change UpgradeCode?
>
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
>
>
>> -Original Message-
>> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
>> Sent: Thursday, December 20, 2012 12:13 PM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>>
>> Okay I changed the ProductCode to be "*" as well as the Package Id="*"
>> First MSI had a version number of 4.0.1.25 second MSI has a version
>> number of 4.1.2.55
>>
>> When I run the second it's like the first one was not installed, it
>> was like running a fresh install... the newer MSI has a different
>> version number
>> (higher) and the ProductCode is different...
>>
>> Steve
>>
>> -Original Message-
>> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
>> Sent: December-20-12 2:55 PM
>> To: General discussion for Windows Installer XML toolset.
>> Subject: Re: [WiX-users] Upgrades NOT working on a new install
>>
>> You need to change ProductCode *and* ProductVersion for a major
>> upgrade to work as you expect. When you change ProductVersion and
>> leave ProductCode the same you have a minor upgrade which requires a
>> different style of install (I'm not expert on installing minor
>> upgrades). The reason it was suggested to set Product/@Id = "*" is so
>> that WiX will automatically create a new guid on every build
>> guaranteeing a major upgrade if and only if you also change ProductVersion 
>> on every build.
>>
>> Edwin G. Castro
>> Software Developer - Staff
>> Digital Channels
>> Fiserv
>> Office: 503-746-0643
>> Fax: 503-617-0291
>> www.fiserv.com
>>
>>
>> > -Original Message-
>> > From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
>> > Sent: Thursday, December 20, 2012 11:26 AM
>> > To: General discussion for Windows Installer XML toolset.
>> > Subject: Re: [WiX-users] Upgrades NOT working on a new install
>> >
>> > Okay,
>> >
>> > I now have:
>> >
>> > > >Name="$(var.PlatformProductName)"
>> >Language="1033"
>> >Version="4.0.2.30"
>> >Manufacturer="$(var.ProductCompany)"
>> >UpgradeCode="$(var.UpgradeCode)">
>> > > >  InstallPrivileges="elevated"
>> >  Manufacturer="$(var.ProductCompany)"
>> >  InstallerVersion="405"
>> >  Compressed="yes"
>> >  InstallScope="perMachine"/>
>> >
>> >
>> > 
>> >  
>> >   > > Property="NEWERVERSIONDETECTED" />
>> >   > > Maximum="$(var.ProductVersion)" IncludeMinimum="yes"
>> > IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" />
>> 
>> >
>> > Where:  in an include file I
>> > include in my product.wxs 
>> >   
>> >   
>> >   
>> >
>> > 
>> >   NOT NEWERVERSIONDETECTED
>> > 
>> >
>> > 
>> >   
>> >
>> > I create one msi with productversion of 4.0.1.25 install it, then
>> > change productversion to 4.0.2.30 and run it and I get the same error:
>> >
>> > "Another version of this product is a

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

No I only change the ProductVersion to a higher number (minor.build) and that 
was it

-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: December-20-12 3:27 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

What do you mean by "When I run the second it's like the first one was not 
installed, it was like running a fresh install"? Does the verbose log tell you 
whether 4.0.1.25 was detected and uninstalled? I guess I should also ask the 
obvious question, did you change UpgradeCode?

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com


> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: Thursday, December 20, 2012 12:13 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> Okay I changed the ProductCode to be "*" as well as the Package Id="*"
> First MSI had a version number of 4.0.1.25 second MSI has a version 
> number of 4.1.2.55
> 
> When I run the second it's like the first one was not installed, it 
> was like running a fresh install... the newer MSI has a different 
> version number
> (higher) and the ProductCode is different...
> 
> Steve
> 
> -Original Message-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: December-20-12 2:55 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> You need to change ProductCode *and* ProductVersion for a major 
> upgrade to work as you expect. When you change ProductVersion and 
> leave ProductCode the same you have a minor upgrade which requires a 
> different style of install (I'm not expert on installing minor 
> upgrades). The reason it was suggested to set Product/@Id = "*" is so 
> that WiX will automatically create a new guid on every build 
> guaranteeing a major upgrade if and only if you also change ProductVersion on 
> every build.
> 
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> 
> 
> > -Original Message-----
> > From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> > Sent: Thursday, December 20, 2012 11:26 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Upgrades NOT working on a new install
> >
> > Okay,
> >
> > I now have:
> >
> >  >Name="$(var.PlatformProductName)"
> >Language="1033"
> >Version="4.0.2.30"
> >Manufacturer="$(var.ProductCompany)"
> >UpgradeCode="$(var.UpgradeCode)">
> >  >  InstallPrivileges="elevated"
> >  Manufacturer="$(var.ProductCompany)"
> >  InstallerVersion="405"
> >  Compressed="yes"
> >  InstallScope="perMachine"/>
> >
> >
> > 
> >  
> >> Property="NEWERVERSIONDETECTED" />
> >> Maximum="$(var.ProductVersion)" IncludeMinimum="yes"
> > IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" />
> 
> >
> > Where:  in an include file I 
> > include in my product.wxs 
> >   
> >   
> >   
> >
> > 
> >   NOT NEWERVERSIONDETECTED
> > 
> >
> > 
> >   
> >
> > I create one msi with productversion of 4.0.1.25 install it, then 
> > change productversion to 4.0.2.30 and run it and I get the same error:
> >
> > "Another version of this product is already installed. Installation 
> > of this version cannot continue. To configure or remove the existing 
> > version of this product, use Add/Remove Programs on the Control Panel"
> >
> > Sigh,
> >
> > Steve
> >
> > -Original Message-
> > From: Neil Sleightholm [mailto:n...@x2systems.com]
> > Sent: December-20-12 1:47 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Upgrades NOT working on a new install
> >
> > You seem to have the MajorUpgrade element and also the Upgrade 
> > element, MajorUpgrade replaces the need for manually authoring the 
> > upgrade table. Also,

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Castro, Edwin G. (Hillsboro)

What do you mean by "When I run the second it's like the first one was not 
installed, it was like running a fresh install"? Does the verbose log tell you 
whether 4.0.1.25 was detected and uninstalled? I guess I should also ask the 
obvious question, did you change UpgradeCode?

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com


> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: Thursday, December 20, 2012 12:13 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> Okay I changed the ProductCode to be "*" as well as the Package Id="*"
> First MSI had a version number of 4.0.1.25 second MSI has a version number
> of 4.1.2.55
> 
> When I run the second it's like the first one was not installed, it was like
> running a fresh install... the newer MSI has a different version number
> (higher) and the ProductCode is different...
> 
> Steve
> 
> -Original Message-
> From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
> Sent: December-20-12 2:55 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> You need to change ProductCode *and* ProductVersion for a major upgrade
> to work as you expect. When you change ProductVersion and leave
> ProductCode the same you have a minor upgrade which requires a different
> style of install (I'm not expert on installing minor upgrades). The reason it 
> was
> suggested to set Product/@Id = "*" is so that WiX will automatically create a
> new guid on every build guaranteeing a major upgrade if and only if you also
> change ProductVersion on every build.
> 
> Edwin G. Castro
> Software Developer - Staff
> Digital Channels
> Fiserv
> Office: 503-746-0643
> Fax: 503-617-0291
> www.fiserv.com
> 
> 
> > -Original Message-
> > From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> > Sent: Thursday, December 20, 2012 11:26 AM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Upgrades NOT working on a new install
> >
> > Okay,
> >
> > I now have:
> >
> >  >Name="$(var.PlatformProductName)"
> >Language="1033"
> >Version="4.0.2.30"
> >Manufacturer="$(var.ProductCompany)"
> >UpgradeCode="$(var.UpgradeCode)">
> >  >  InstallPrivileges="elevated"
> >  Manufacturer="$(var.ProductCompany)"
> >  InstallerVersion="405"
> >  Compressed="yes"
> >  InstallScope="perMachine"/>
> >
> >
> > 
> >  
> >> Property="NEWERVERSIONDETECTED" />
> >> Maximum="$(var.ProductVersion)" IncludeMinimum="yes"
> > IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" />
> 
> >
> > Where:  in an include file I
> > include in my product.wxs 
> >   
> >   
> >   
> >
> > 
> >   NOT NEWERVERSIONDETECTED
> > 
> >
> > 
> >   
> >
> > I create one msi with productversion of 4.0.1.25 install it, then
> > change productversion to 4.0.2.30 and run it and I get the same error:
> >
> > "Another version of this product is already installed. Installation of
> > this version cannot continue. To configure or remove the existing
> > version of this product, use Add/Remove Programs on the Control Panel"
> >
> > Sigh,
> >
> > Steve
> >
> > -Original Message-
> > From: Neil Sleightholm [mailto:n...@x2systems.com]
> > Sent: December-20-12 1:47 PM
> > To: General discussion for Windows Installer XML toolset.
> > Subject: Re: [WiX-users] Upgrades NOT working on a new install
> >
> > You seem to have the MajorUpgrade element and also the Upgrade
> > element, MajorUpgrade replaces the need for manually authoring the
> > upgrade table. Also, I wouldn't hard code Product/@Id just use "*" and
> > have WiX generate it for you, likewise Package/@Id isn't required just
> > let WiX do it.
> >
> > Neil
> >
> > -Original Message-
> > From: StevenOgilvie [mailto:sogil...@msn.com]
> > Sent: 20 December 2012 18:26
> > To: wix-users@lists.

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

Okay I changed the ProductCode to be "*" as well as the Package Id="*"
First MSI had a version number of 4.0.1.25 second MSI has a version number of 
4.1.2.55

When I run the second it's like the first one was not installed, it was like 
running a fresh install... the newer MSI has a different version number 
(higher) and the ProductCode is different...

Steve

-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] 
Sent: December-20-12 2:55 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You need to change ProductCode *and* ProductVersion for a major upgrade to work 
as you expect. When you change ProductVersion and leave ProductCode the same 
you have a minor upgrade which requires a different style of install (I'm not 
expert on installing minor upgrades). The reason it was suggested to set 
Product/@Id = "*" is so that WiX will automatically create a new guid on every 
build guaranteeing a major upgrade if and only if you also change 
ProductVersion on every build.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com


> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: Thursday, December 20, 2012 11:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> Okay,
> 
> I now have:
> 
> Name="$(var.PlatformProductName)"
>Language="1033"
>Version="4.0.2.30"
>Manufacturer="$(var.ProductCompany)"
>UpgradeCode="$(var.UpgradeCode)">
>   InstallPrivileges="elevated"
>  Manufacturer="$(var.ProductCompany)"
>  InstallerVersion="405"
>  Compressed="yes"
>  InstallScope="perMachine"/>
> 
> 
> 
>  
>Property="NEWERVERSIONDETECTED" />
>Maximum="$(var.ProductVersion)" IncludeMinimum="yes"
> IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" /> 
> 
> Where:  in an include file I 
> include in my product.wxs 
>   
>   
>   
> 
> 
>   NOT NEWERVERSIONDETECTED
> 
> 
> 
>   
> 
> I create one msi with productversion of 4.0.1.25 install it, then 
> change productversion to 4.0.2.30 and run it and I get the same error:
> 
> "Another version of this product is already installed. Installation of 
> this version cannot continue. To configure or remove the existing 
> version of this product, use Add/Remove Programs on the Control Panel"
> 
> Sigh,
> 
> Steve
> 
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: December-20-12 1:47 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> You seem to have the MajorUpgrade element and also the Upgrade 
> element, MajorUpgrade replaces the need for manually authoring the 
> upgrade table. Also, I wouldn't hard code Product/@Id just use "*" and 
> have WiX generate it for you, likewise Package/@Id isn't required just 
> let WiX do it.
> 
> Neil
> 
> -Original Message-
> From: StevenOgilvie [mailto:sogil...@msn.com]
> Sent: 20 December 2012 18:26
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Upgrades NOT working on a new install
> 
> Hi all,
> 
> I have implemented upgrades by doing the following (I have an include 
> file that has the product/package properties which I define and 
> include the include file :)...
> 
> Name="$(var.PlatformProductName)"
>Language="1033"
>Version="4.0.1.25"
>Manufacturer="$(var.ProductCompany)"
>UpgradeCode="$(var.UpgradeCode)">
>   InstallPrivileges="elevated"
>  Manufacturer="$(var.ProductCompany)"
>  InstallerVersion="405"
>  Compressed="yes"
>  InstallScope="perMachine"/>Schedule="afterInstallInitialize"
>   DowngradeErrorMessage="A later version of
> $(var.PlatformProductName) is already installed. Setup will now 
> exit."/>
> 
> then:
> 
>Property="NEWERVERSIONDETECTED" />
>Maximum="$(var.ProductVersion)"
>

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Castro, Edwin G. (Hillsboro)

You need to change ProductCode *and* ProductVersion for a major upgrade to work 
as you expect. When you change ProductVersion and leave ProductCode the same 
you have a minor upgrade which requires a different style of install (I'm not 
expert on installing minor upgrades). The reason it was suggested to set 
Product/@Id = "*" is so that WiX will automatically create a new guid on every 
build guaranteeing a major upgrade if and only if you also change 
ProductVersion on every build.

Edwin G. Castro
Software Developer - Staff
Digital Channels
Fiserv
Office: 503-746-0643
Fax: 503-617-0291
www.fiserv.com


> -Original Message-
> From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
> Sent: Thursday, December 20, 2012 11:26 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> Okay,
> 
> I now have:
> 
> Name="$(var.PlatformProductName)"
>Language="1033"
>Version="4.0.2.30"
>Manufacturer="$(var.ProductCompany)"
>UpgradeCode="$(var.UpgradeCode)">
>   InstallPrivileges="elevated"
>  Manufacturer="$(var.ProductCompany)"
>  InstallerVersion="405"
>  Compressed="yes"
>  InstallScope="perMachine"/>
> 
> 
> 
>  
>Property="NEWERVERSIONDETECTED" />
>Maximum="$(var.ProductVersion)" IncludeMinimum="yes"
> IncludeMaximum="no" Property="OLDERVERSIONBEINGUPGRADED" />
> 
> 
> Where:  in an include file I include in
> my product.wxs 
>   
>   
>   
> 
> 
>   NOT NEWERVERSIONDETECTED
> 
> 
> 
>   
> 
> I create one msi with productversion of 4.0.1.25 install it, then change
> productversion to 4.0.2.30 and run it and I get the same error:
> 
> "Another version of this product is already installed. Installation of this
> version cannot continue. To configure or remove the existing version of this
> product, use Add/Remove Programs on the Control Panel"
> 
> Sigh,
> 
> Steve
> 
> -Original Message-
> From: Neil Sleightholm [mailto:n...@x2systems.com]
> Sent: December-20-12 1:47 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Upgrades NOT working on a new install
> 
> You seem to have the MajorUpgrade element and also the Upgrade
> element, MajorUpgrade replaces the need for manually authoring the
> upgrade table. Also, I wouldn't hard code Product/@Id just use "*" and have
> WiX generate it for you, likewise Package/@Id isn't required just let WiX do
> it.
> 
> Neil
> 
> -Original Message-
> From: StevenOgilvie [mailto:sogil...@msn.com]
> Sent: 20 December 2012 18:26
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] Upgrades NOT working on a new install
> 
> Hi all,
> 
> I have implemented upgrades by doing the following (I have an include file
> that has the product/package properties which I define and include the
> include file :)...
> 
> Name="$(var.PlatformProductName)"
>Language="1033"
>Version="4.0.1.25"
>Manufacturer="$(var.ProductCompany)"
>UpgradeCode="$(var.UpgradeCode)">
>   InstallPrivileges="elevated"
>  Manufacturer="$(var.ProductCompany)"
>  InstallerVersion="405"
>  Compressed="yes"
>  InstallScope="perMachine"/>Schedule="afterInstallInitialize"
>   DowngradeErrorMessage="A later version of
> $(var.PlatformProductName) is already installed. Setup will now exit."/>
> 
> then:
> 
>Property="NEWERVERSIONDETECTED" />
>Maximum="$(var.ProductVersion)"
>   IncludeMinimum="yes" IncludeMaximum="no"
>   Property="OLDERVERSIONBEINGUPGRADED" /> 
> where I have the following defined:
> 
> 
> and have a productcode and upgradecode that I don't change...
> 
> customactions:
> 
>  Value="amus"
> />
> 
>   CA: Setting REINSTALLMODE to
> amus...
> 
> 
> 
>   CA: Setting up
> NEWAPPFOUND...
> 
> 
> 
>   
>   
>   
>After="FindRelatedProducts">NEWAPPFOUND
> 
> 
>   NOT NEWERVER

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Steven Ogilvie

Okay,

I now have:






 
  
  


Where:  in an include file I include in 
my product.wxs

  
  
  


  NOT NEWERVERSIONDETECTED



  

I create one msi with productversion of 4.0.1.25 install it, then change 
productversion to 4.0.2.30 and run it and I get the same error:

"Another version of this product is already installed. Installation of this 
version cannot continue. To configure or remove the existing version of this 
product, use Add/Remove Programs on the Control Panel"

Sigh,

Steve

-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com] 
Sent: December-20-12 1:47 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Upgrades NOT working on a new install

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com]
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades NOT working on a new install....

2012-12-20 Thread Neil Sleightholm

You seem to have the MajorUpgrade element and also the Upgrade element, 
MajorUpgrade replaces the need for manually authoring the upgrade table. Also, 
I wouldn't hard code Product/@Id just use "*" and have WiX generate it for you, 
likewise Package/@Id isn't required just let WiX do it.

Neil

-Original Message-
From: StevenOgilvie [mailto:sogil...@msn.com] 
Sent: 20 December 2012 18:26
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades NOT working on a new install

Hi all,

I have implemented upgrades by doing the following (I have an include file that 
has the product/package properties which I define and include the include file 
:)...


 

then:

  
where 
I have the following defined:


and have a productcode and upgradecode that I don't change...

customactions:



  CA: Setting REINSTALLMODE to 
amus...



  CA: Setting up 
NEWAPPFOUND...



  
  
  
  NEWAPPFOUND


  NOT NEWERVERSIONDETECTED



  
  NEWAPPFOUND

I then built the .MSI and installed it...

I then changed the product version to 4.0.2.30 and change the Package ID to 
another GUID re built the .MSI and launched it...

Instead of a message regarding upgrade minor I get a message: "Another version 
of this product is already installed. Installation of this version cannot 
continue. To configure or remove the existing version of this product, use 
Add/Remove Programs on the Control Panel"

What am I doing wrong? I followed the suggestions from:
http://wix.tramontana.co.hu/tutorial/upgrades-and-modularization

This is a new install so I was just making sure I had upgrades covered for down 
the road :(

thanks,

STeve






--
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Upgrades-NOT-working-on-a-new-install-tp7582496.html
Sent from the wix-users mailing list archive at Nabble.com.

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely 
access PCs and mobile devices and provide instant support Improve your 
efficiency, and focus on delivering more value-add services Discover what IT 
Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades

2009-03-09 Thread Pally Sandher

Changing the GUID of your component makes no difference to anything in
your example. Your code is telling the Windows Installer to uninstall
any old version of your software before it installs the current version.
If this is the only way your installers will work then your GUIDs can be
the same or different regardless. To the best of my knowledge you should
not need to care about component GUIDs unless you are planning on
patching using MSP's.


Palbinder Sandher 
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500 
F: +44 (0) 141 945 8501 

http://www.iesve.com 
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456 
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
 
 

-Original Message-
From: Lough, Norman [mailto:norman.lo...@imass.co.uk] 
Sent: 09 March 2009 13:37
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Upgrades

The code below clears out previous versions for me.

 



 

...

 







  



 

...



  

  



 

...

 

 

I ran a test where I went from  Version 1.0.3.0 to 1.0.4.0. In the
1.0.3.0 version the root directory contained 3 files Default.aspx,
Web.Config and TextFile1.Txt. In Version 1.0.4.0 I no longer included
TextFile1.Txt. The product code changed (I left the upgrade codes as
before). I changed the guid for the root directory component to see what
would happen when Version 1.0.4.0 was installed over the top of 1.0.3.0.
Even though the guid changed the original file TextFile1.Txt no longer
remained  - I suppose this is to be expected since as far as 1.0.4.0 is
concerned TextFile1.Txt is not part of its installation.

 

Could someone explain if there is any significance attached to me
changing the guid of the root directory (or any other directory
component) in this context. The reason I ask is that I'm looking to
automate the wxs file creation based on a periodic publication of a
website. It seems from the above that I can just create the guids for
these directory components on the fly rather than maintain a record of
previous folders/components (some of which may or may not persist)? 

 

 



 

  

  

  





 ...

 

 

Thanks

Norman Lough

Developer

Tel: +44 (0)191 213 

DDI: +44 (0)191 2028360

Email: norman.lo...@imass.co.uk

Imass Ltd, Northumbria House, Regent Centre, Gosforth, Newcastle upon
Tyne, NE3 3PX. http://www.imass.co.uk  

 

Imass Limited is an Infoterra company, part of EADS Astrium

 

 

Registered in England and Wales No. 2379476

 

- Disclaimer -
The information contained in this e-mail and its attachments is
confidential and intended only for the use of the individual or entity
named above.  If you are not the intended recipient, please do not read,
copy, use or disclose this message or its attachments.  If you have
received this message in error, please notify the sender immediately and
delete or destroy all copies of this message and attachments in all
media.  Any views expressed in this e-mail that do not relate to Imass'
official business may not reflect the views of the company.

 


--
Open Source Business Conference (OSBC), March 24-25, 2009, San
Francisco, CA -OSBC tackles the biggest issue in open source: Open
Sourcing the Enterprise -Strategies to boost innovation and cut costs
with open source participation -Receive a $600 discount off the
registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades... during RemoveExistingProducts action CA's don't have access to _any_ properties?

2006-11-12 Thread Tina Basinger

Two thoughts that I have.  
 
1.  Your SetCAP_RestoreWebConfig custom action is sequenced at 265.  Has the TargetDir property been determined by Windows Installer at this point?  If it hasn't, then you're going to be getting a blank TargetDir value.  I"m not real sure of when that happens, but that's a thought of what might be happening.
2.  Your BackupWebConfig custom action is executed as deferred.  Deferred custom actions cannot get or set the normal MSI properties.  They can only use the CustomActionData property to pass information from the install into the custom action.  So, for this reason, the msgbox displaying TARGETDIR may be correctly displaying a blank string.  And, for the reason mentioned in item 1, your message box displaying CustomActionData could also be correctly displaying a blank string.

 
Finally, to get a better idea of what is really happening, run your upgrade installation with verbose logging turned on.  (msiexec /l*v Log.txt /i ProductName.msi).   Then read your log file to determine what the value of TARGETDIR actually is during the uninstall, and possibly when it gets set.  

 
Hope this helps.
-Tina
 
 
On 11/9/06, Rob MacFadyen <[EMAIL PROTECTED]> wrote:
Hey all,I'm trying to implement handling for major upgrades for a web applicationinstallation.
The use case I'm currently testing is:1. User installs v1.0.0 of the application   - Install gathers information about the virtual directory and database server   - App is installed, vdir created, db created,
 web.config is updated with connection string and encrypted2. User installs v1.0.1 of the application   - no prompts for virtual directory or database server (upgrading... should use existing
 vdir and db).   - Old version is removed as part of the install.The challenge I'm facing is the web.config file... I _need_ to keep thecurrent version from the v1.0.0 install.So... I've decided that during Uninstall, if uninstalling because of a
backup, a backup of the web.config file will be made (filesystemobjectcopyfile). This isn't working out at all... the CA seem to get the TARGETDIRproperty.Here's the backup CA definition:   Id="BackupWebConfig"   Return="check"   Execute="deferred"   Impersonate="yes"   BinaryKey="Callwebconfig"   _vbscript_Call="Backup"
/>   Id="SetCAP_BackupWebConfig"   Property="BackupWebConfig"   Value="[TARGETDIR]"/>Here's the relevant InstallExecuteSequence entries:
... snip ...
REMOVE="ALL" AND UPGRADINGPRODUCTCODEIn the _vbscript_ I have the following debug messages:
msgbox "CustomActionData: " & Session.Property("CustomActionData")msgbox "TARGETDIR: " & Session.Property("TARGETDIR")Both of which display empty strings!
So... from my point of view... it looks like an uninstall that is initiatedby RemoveExistingProducts doesn't quite operate like a normal uninstall...but that doesn't make much sense.Anyone have any suggestions?
Regards,Rob-Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___WiX-users mailing listWiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades All/Current User

2006-08-12 Thread Bob Arnson

[EMAIL PROTECTED] wrote:
> I have an MSI file with a user-interface that gives the choice to install for 
> all users or only for current user. When the user installs a new version of 
> the product there should be the choice to remove the older version or to 
> continue with installation and install both versions (for any reasons). The 
> user should have this choice in any case, no matter if he selected "all 
> users" or "current user" in the previous version.
>
> Is it possible to realise this with wix/msi?
>   
No. Major upgrades don't work across contexts (e.g., per-user, per-machine).

-- 
sig://boB
http://bobs.org

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Re: [WiX-users] Upgrades

Re: [WiX-users] Upgrades

Re: [WiX-users] Upgrades

Re: [WiX-users] Upgrades...

Re: [WiX-users] Upgrades...

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades NOT working on a new install....

Re: [WiX-users] Upgrades

Re: [WiX-users] Upgrades... during RemoveExistingProducts action CA's don't have access to _any_ properties?

Re: [WiX-users] Upgrades All/Current User

22 matches

Site Navigation

Mail list logo

Footer information