On Tue, 30 Jul 2013 21:50:54 -0700, Blair Murri wrote:
> You can use the MajorUpgrade element (use the UpgradeCode you prefer in your
> Product element) and
> use just the offending UpgradeCode in the Upgrade element (to find/remove
> versions using it).
Blair,
I tried that but end up with two rows for the good code in my Upgrade table.
Below is my code - am I doing something wrong or does it just not work?
....
<Product
Id="$(var.ProductCode)"
Name="$(var.ProductName)"
Language="$(var.Language)"
Version="$(var.ProductVersion)"
UpgradeCode="$(var.UpgradeCode)"
Manufacturer="$(var.Manufacturer)"
>
<Package
Id="*"
InstallerVersion="301"
Compressed="yes"
InstallScope="$(var.InstallScope)"
Manufacturer="$(var.Manufacturer)"
Description="$(var.Description)"
Keywords="$(var.Keywords)"
Comments="(var.CopyRight)" />
<MajorUpgrade
Schedule="afterInstallExecute"
DowngradeErrorMessage="A newer version of [ProductName] is already
installed." />
<Upgrade Id="$(var.WrongUpgradeCode)" />
...
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
