In article <[EMAIL PROTECTED]>,
"Colin Bleckner" <[EMAIL PROTECTED]> writes:
> Which means that what I'm doing isn't a great long term solution. Is there
> another way to guarantee that my product will replace all of my previous
> ones without bumping the max version on every build?
Product version comparisons use the first three fields of the
four-field version number, so 1.0.1.x will upgrade 1.0.0.x.
So yes, switch your product code, leave your Upgrade table populated
with the product code for your previous builds so that those products
are removed when you install this product.
Then pick a version number back to 1.0.0 and just increment the
smallest field on each build.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
