[wix-users] Shouldn't burn verify the bundle's digital signature? (3.10)
bob at firegiant.com
Wed Apr 26 08:57:19 PDT 2017
Handle OnCacheVerifyComplete and you can provide whatever UI you want, very early in the apply phase.
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Jon Seanor
Sent: Wednesday, 26 April, 2017 11:40
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] Shouldn't burn verify the bundle's digital signature? (3.10)
It's unfortunate that it doesn't check before cache verification.
The resulting end-user facing message (a common dlg asking for a file) results in support calls.
It *should* be simple for the engine to perform a signature check (assuming it was not itself damaged).
I was hoping I could write a ba to do this, but looking at balExtension\wixstdba it doesn't look like it has access to the source bundle path.
On 26 April 2017 at 15:14, Nir Bar <nir.bar at panel-sw.com> wrote:
> The bootstrapper is made of the burn engine plus embedded containers
> that hold the files.Once launched, burn extracts the engine to a
> temporary folder and then launches it.
> When the user starts applying, the engine extracts the containers to
> cache folder and installs the packages.
> Assuming that the file was corrupted anywhere other than the engine
> itself, burn will find it on cache verification phase only
> Nir Bar
> Panel::Software Architecture and Development
> JetBA.net- Native and WPF WiX BootstrapperApplication Frameworks
> WiX Toolset Users Mailing List provided by FireGiant
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/
More information about the wix-users