The question is, whether this holds true for Small Updates, since Microsoft writes that ProductVersion must not be modified. So is it a valid assumption (that holds true forever and not just by incident is at the moment so) that the ignoring described in the link you posted also is in place for Small Updates?
> -----Original Message----- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Freitag, 9. April 2010 11:59 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] ProductVersion / Small Updates > > Windows Installer only uses the first 3 fields of version numbers so > you > can change the 4th one as much as you'd like. See -> > http://msdn.microsoft.com/en-us/library/aa370859.aspx > > Personally I stay away from Small Updates for this reason. Minor > upgrades work just as well with no ambiguity. > > 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 <Virtual Environment>** > 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: Markus Karg [mailto:k...@quipsy.de] > Sent: 09 April 2010 09:11 > To: General discussion for Windows Installer XML toolset. > Subject: [WiX-users] ProductVersion / Small Updates > > AFAIK for a small update (not minor upgrade) the version number of a > product must not change. The problem is: How to identify which version > (the original or the patched one) is installed now? > > > > Maybe I misunderstood the contraint about version numbers, so I *may* > change the ProductVersion, but I *must not* modify major.minor but only > the postfixed fraction (major.minor.x.y)? > > > > ----------------------------------------------------------------------- > - > ------ > Download Intel® Parallel Studio Eval Try the new software tools > for > yourself. Speed compiling, find bugs proactively, and fine-tune > applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ----------------------------------------------------------------------- > ------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
