Hey again Blaine,
> Si - I wasn't as clear as I meant to be before.
> Because our automated packager builds at least 2 MSI's a day per product
> and has built up to 6 versions in a day when we are close to deadline I
> really don't want to open and update Wix by hand to change the
> variables.
the old values in
a DB or log file. What are others doing?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of si
Sent: Thursday, March 06, 2008 12:26 AM
To: Wheeler, Blaine (DSHS/DCS)
Cc: WiX Users
Subject: Re: [WiX-users] Preventing upgrades for version
Hi Blaine, cc'd to list.
> I really like your code sample, particularly the use of the variables.
> Which raises a question about managing sequential-multiple builds. May
> I ask how you get the $(var.ProductVersion) and
> $(var.PreviousProductVersion) to pass into Wix?
They're just WiX varia
Hi,
We're currently experimenting with various upgrade strategies. So far
I like the simplicity of the "Major Upgrade" only approach.
One option we're looking at is that due to the potential for database
changes, e.g. db schema changes and data conversion scripts, we don't
want the installer to
4 matches
Mail list logo
