Created SF Feature Request 3472491:
https://sourceforge.net/tracker/?func=detail&aid=3472491&group_id=105970&atid=642717
https://sourceforge.net/tracker/?func=detail&aid=3472491&group_id=105970&atid=642717
.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabb
Yep, reasonable.
On Wed, Jan 11, 2012 at 6:28 AM, jhennessey wrote:
> I can also verify that BootstrapperApplicationData.xml doesn't contain the
> payload information...it's in the manifest file.
>
> I think it would be advantageous to include all of the information from the
> manifest in the Boo
I can also verify that BootstrapperApplicationData.xml doesn't contain the
payload information...it's in the manifest file.
I think it would be advantageous to include all of the information from the
manifest in the BootstrapperApplicationData.xml file (or at least write the
manifest to the tempo
Rob Mensching-7 wrote
>
> The BootstrapperApplication.xml should list all the payloads, so if you
> really want to do this upfront, your BA should be able to it (plus using
> the WixBundleOriginalPath variable).
>
In the temporary folder I found a file BootstrapperApplicationData.xml. I
guess t
Hmm, yeah, Burn doesn't validate the source until it knows exactly what it
needs (aka: after Plan).
The BootstrapperApplication.xml should list all the payloads, so if you
really want to do this upfront, your BA should be able to it (plus using
the WixBundleOriginalPath variable).
On Tue, Jan 10,
In our MBA we implemented a setup wizard with a feature selection on the
first step. My intention was to give a hint to the user in case of missing
or invalid packages *before* he entered the necessary information and the
installation actually begins.
Rob Mensching-7 wrote
>
> 1. If a package ca
1. If a package cannot be found, you will get a source resolution callback.
2. At the very least Burn does a SHA1 hash of the files to verify they are
correct before installing them for security reasons. If you digitally sign
your payloads, Burn will verify the signatures instead of hashing (which
Hi,
We created several bootstrapper projects, which include some MSI packages
with option Compressed='no'. As a result the MSIs have to be:
1) available on the file system at the right location (relative to the
bootstrapper) and
2) available in the right version (which means it has to be exactly
8 matches
Mail list logo