Sorry. Thanks for the correction.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Predicting-Bootstrapper-Cache-Location-tp7599709p7599736.html
Sent from the wix-users mailing list archive at Nabble.com.
I described one approach in this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Burn-managing-installed-products-after-initial-install-td7595346.html#a7595368
.
--
View this message in context:
Message-
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Thursday, March 26, 2015 7:11 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Predicting Bootstrapper Cache Location
I described one approach in this thread
http://windows-installer-xml-wix-toolset.687559.n2
the WiX toolset.
Subject: Re: [WiX-users] Predicting Bootstrapper Cache Location
Jacob,
You mentioned something interesting that I can't get to work. I tried
Chain
MsiPackage SourceFile=$(var.projectName.TargetPath)
MsiProperty Name=BUNDLEPROVIDERKEY Value=[WixBundleProviderKey
Castro [mailto:egca...@gmail.com]
Sent: Thursday, March 26, 2015 11:51 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] Predicting Bootstrapper Cache Location
Jacob,
You mentioned something interesting that I can't get to work. I tried
Chain
MsiPackage SourceFile
The remarks at
http://wixtoolset.org/documentation/manual/v3/xsd/dependency/providerkey.html
say
This provider key is designed to persist throughout compatible upgrades so
that dependent bundles do not have to be reinstalled and *will not prevent
your product from being upgraded*. If this
Phill's comment was incorrect, the provider key will be generated for you
automatically if you don't specify it.
This behavior is a bug that I'm currently working on:
http://wixtoolset.org/issues/4630/
On Thu, Mar 26, 2015 at 7:06 PM, Edwin Castro egca...@gmail.com wrote:
The remarks at
This post may help:
http://stackoverflow.com/questions/17269942/not-possible-to-pass-wixbundleproviderkey-variable-to-msipackage
-
Nir Bar
Freelance Developer
Mail: nir@panel-sw.com
Web: www.panel-sw.com
- C++ On Windows, Linux and Embedded Platforms
- WiX InstallShield
--
So it looks like the bootstrapper is not passing BUNDLEPROVIDERKEY to the
MSI at all.
You need to define Bundle/@ProviderKey, here
http://wixtoolset.org/documentation/manual/v3/xsd/wix/bundle.html . I
set it to a GUID (and like UpgradeCode I do not change the
Bundle/@ProviderKey between
@lists.sourceforge.net
Subject: Re: [WiX-users] Predicting Bootstrapper Cache Location
I described one approach in this thread
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Burn-managing-installed-products-after-initial-install-td7595346.html#a7595368
.
--
View this message
10 matches
Mail list logo