[WiX-users] Setup upgrade needs to care for 4th part of version number

2009-07-13 Thread Dirk Ziegelmeier
Hello All,

due to political issues (see below) my setups need to be able to upgrade
when only the 4th part of the version info changes.

Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major
upgrades, the product GUI always changes (that is OK and not an issue to
discuss).

After a lot of googeling, my idea is to write a custom action that can to
the version comparision, but then I need to tell MSI somehow at runtime that
this run is an upgrade - how can I do that?

Is there another (better?) way to achieve this?


Thank you in advance
Dirk

PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision.
During the development phase only the SVN revision will increase. My bosses
install the setups on their PCs and do not always want to uninstall by hand
before installing a new Setup...
--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

2009-07-13 Thread Neil Sleightholm
I had a similar problem the way I got round it was to set the upgrade code to 
include the maximum version, e.g. UpgradeVersion/@IncludeMaximum=yes. This 
will generate an ICE61 which you will need to ignore. This isn't perfect as 
1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two releases with the 
same 3 part number will never go live you should be ok.
 
If you search back through the list you should find a discussion about doing 
this.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com 
 



From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net]
Sent: Mon 13/07/2009 12:42
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Setup upgrade needs to care for 4th part of version number



Hello All,

due to political issues (see below) my setups need to be able to upgrade
when only the 4th part of the version info changes.

Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major
upgrades, the product GUI always changes (that is OK and not an issue to
discuss).

After a lot of googeling, my idea is to write a custom action that can to
the version comparision, but then I need to tell MSI somehow at runtime that
this run is an upgrade - how can I do that?

Is there another (better?) way to achieve this?


Thank you in advance
Dirk

PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision.
During the development phase only the SVN revision will increase. My bosses
install the setups on their PCs and do not always want to uninstall by hand
before installing a new Setup...
--
Enter the BlackBerry Developer Challenge 
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/Challenge
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

2009-07-13 Thread Dirk Ziegelmeier
Hello Neil,

thank you - I didn't find this one. It is not perfect, but sufficiently good
:-). If someone can tell me the perfect solution, I'm still open to it.

Thanks again!
Dirk



On Mon, Jul 13, 2009 at 12:00, Neil Sleightholm n...@x2systems.com wrote:

 I had a similar problem the way I got round it was to set the upgrade code
 to include the maximum version, e.g. UpgradeVersion/@IncludeMaximum=yes.
 This will generate an ICE61 which you will need to ignore. This isn't
 perfect as 1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two
 releases with the same 3 part number will never go live you should be ok.

 If you search back through the list you should find a discussion about
 doing this.

 Neil

 Neil Sleightholm
 X2 Systems Limited
 n...@x2systems.com mailto:n...@x2systems.com


 

 From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net]
 Sent: Mon 13/07/2009 12:42
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Setup upgrade needs to care for 4th part of version
 number



 Hello All,

 due to political issues (see below) my setups need to be able to upgrade
 when only the 4th part of the version info changes.

 Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major
 upgrades, the product GUI always changes (that is OK and not an issue to
 discuss).

 After a lot of googeling, my idea is to write a custom action that can to
 the version comparision, but then I need to tell MSI somehow at runtime
 that
 this run is an upgrade - how can I do that?

 Is there another (better?) way to achieve this?


 Thank you in advance
 Dirk

 PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision.
 During the development phase only the SVN revision will increase. My bosses
 install the setups on their PCs and do not always want to uninstall by hand
 before installing a new Setup...

 --
 Enter the BlackBerry Developer Challenge
 This is your chance to win up to $100,000 in prizes! For a limited time,
 vendors submitting new applications to BlackBerry App World(TM) will have
 the opportunity to enter the BlackBerry Developer Challenge. See full prize
 details at: http://p.sf.net/sfu/Challenge
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



 --
 Enter the BlackBerry Developer Challenge
 This is your chance to win up to $100,000 in prizes! For a limited time,
 vendors submitting new applications to BlackBerry App World(TM) will have
 the opportunity to enter the BlackBerry Developer Challenge. See full prize
 details at: http://p.sf.net/sfu/Challenge
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Setup upgrade needs to care for 4th part of version number

2009-07-13 Thread Neil Sleightholm
The perfect solution would be for Windows Installer to understand 4 part 
version numbers like every other system on the planet :-)
 
One other point, I schedule RemoveExistingProducts after InstallValidate, it 
gets a bit more messy if this is not the case.
 
Neil
 
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com mailto:n...@x2systems.com 
 



From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net]
Sent: Mon 13/07/2009 13:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Setup upgrade needs to care for 4th part of version 
number



Hello Neil,

thank you - I didn't find this one. It is not perfect, but sufficiently good
:-). If someone can tell me the perfect solution, I'm still open to it.

Thanks again!
Dirk



On Mon, Jul 13, 2009 at 12:00, Neil Sleightholm n...@x2systems.com wrote:

 I had a similar problem the way I got round it was to set the upgrade code
 to include the maximum version, e.g. UpgradeVersion/@IncludeMaximum=yes.
 This will generate an ICE61 which you will need to ignore. This isn't
 perfect as 1.2.3.4 will be downgraded by 1.2.3.3 but if you are sure two
 releases with the same 3 part number will never go live you should be ok.

 If you search back through the list you should find a discussion about
 doing this.

 Neil

 Neil Sleightholm
 X2 Systems Limited
 n...@x2systems.com mailto:n...@x2systems.com


 

 From: Dirk Ziegelmeier [mailto:d...@ziegelmeier.net]
 Sent: Mon 13/07/2009 12:42
 To: wix-users@lists.sourceforge.net
 Subject: [WiX-users] Setup upgrade needs to care for 4th part of version
 number



 Hello All,

 due to political issues (see below) my setups need to be able to upgrade
 when only the 4th part of the version info changes.

 Example: V1.0.0.1 needs to upgrade V1.0.0.0. My installers always do major
 upgrades, the product GUI always changes (that is OK and not an issue to
 discuss).

 After a lot of googeling, my idea is to write a custom action that can to
 the version comparision, but then I need to tell MSI somehow at runtime
 that
 this run is an upgrade - how can I do that?

 Is there another (better?) way to achieve this?


 Thank you in advance
 Dirk

 PS: Political issue explanation: We label Major.Minor.Bugfix.SvnRevision.
 During the development phase only the SVN revision will increase. My bosses
 install the setups on their PCs and do not always want to uninstall by hand
 before installing a new Setup...

 --
 Enter the BlackBerry Developer Challenge
 This is your chance to win up to $100,000 in prizes! For a limited time,
 vendors submitting new applications to BlackBerry App World(TM) will have
 the opportunity to enter the BlackBerry Developer Challenge. See full prize
 details at: http://p.sf.net/sfu/Challenge
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users



 --
 Enter the BlackBerry Developer Challenge
 This is your chance to win up to $100,000 in prizes! For a limited time,
 vendors submitting new applications to BlackBerry App World(TM) will have
 the opportunity to enter the BlackBerry Developer Challenge. See full prize
 details at: http://p.sf.net/sfu/Challenge
 ___
 WiX-users mailing list
 WiX-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wix-users

--
Enter the BlackBerry Developer Challenge 
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize 
details at: http://p.sf.net/sfu/Challenge
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


--
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users