It is very controlled, major minor are the application version, build changes daily and revision on each build - that is a very common scenario and I don't at all see that as "terrifying". I have looked at various version schemes and this is only one that works reliably from build to build, is idempotent and does not rely on artefacts in source control. If you can come up with a better versioning scheme I'd love to hear it.
This is not a management thing; this is a sensible design decision made because the Windows Installer team made the most ridiculous decision not to support the 4 version part. We never do more than one release to the public in a day and if the test team have to be careful that is ok. Neil -----Original Message----- From: Rob Mensching [mailto:r...@robmensching.com] Sent: 16 January 2011 16:55 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Wix upgrade process does not consider 4th part of the version string Terrifying. You must be in some really controlled environments for that to work out well. <smile/> The Windows Installer (for whatever reason) chose to ignore the 4th version. It boggles my mind that "management" gets to decide a versioning scheme that won't work. You might as well pick a different installation technology that meets the requirement than the Windows Installer if something so fundamental as versioning is going to be ignored. The cognitive dissonance here kills me. <smile/> On Sun, Jan 16, 2011 at 7:07 AM, Neil Sleightholm <n...@x2systems.com>wrote: > I have a similar scenario and my workaround is to allow same version > upgrades. This means 3.0.1.14900 will upgrade 3.0.1.14500 (but it also > means 3.0.1.14500 will upgrade 3.0.1.14900 which might be undesirable). > > In WiX 3.5 you can do this by setting > MajorUpgrade/@AllowSameVersionUpgrades - otherwise just set the > appropriate fields in the Upgrade table. > > Neil > > -----Original Message----- > From: Sanjay Rao [mailto:s...@noida.interrasystems.com] > Sent: 14 January 2011 21:33 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] Wix upgrade process does not consider 4th part of > the version string > > Hi, > > I have an installer having 4-part version strings. Our installer stops > installation if a newer version is already installed on the system. We > often have alpha/beta releases of our product in which we do not > change first 3 parts of the product. Suppose we have two releases of > our product : > Release1 : 3.0.1.14500(Alpha) > Release2 : 3.0.1.14900(Beta) > > Our users are able to install alpha release even if beta is already > present on their systems. > I went through this article > http://wix.sourceforge.net/manual-wix3/major_upgrade.htm > see the paragraph having text "Windows Installer only uses the first 3 > parts of the............" > > Is there any way in Wix to take care of 4th part of version string in > upgrade process ? > OR > Do I need to dive into clumsy custom action thing to take care this ? > > Regards, > Sanjay Rao > > -- > Sanjay Rao > Digital Media Group, Interra Systems > s...@interrasystems.com > Phone: +1-408-873-1212 > http://www.interrasystems.com > > ---------------------------------------------------------------------- > -- > ------ > Protect Your Site and Customers from Malware Attacks Learn about > various malware tactics and how to avoid them. Understand malware > threats, the impact they can have on your business, and how you can > protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ---------------------------------------------------------------------- > -------- Protect Your Site and Customers from Malware Attacks Learn > about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how > you can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------ ------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
