[wix-devs] 4991 - Handling of related bundles missing from cache

[Bob Arnson]

1. Why care about file size (i.e., isn't hash sufficient)?
2. Why skip BA notification if we didn't record the hash/size? Is there a reason to let the BA know in that case? (Maybe it wants to cancel and say 'go download v1.0 again to uninstall'?)
3. The mismatch between stripped bundle and downloadable bundle seems like it's more of a roadblock than a speed bump. (Is the .exe that gets cached identical if it has no attached containers other than the UX container? If so, that might be a semi-viable workaround but even that's problematic because of the constantly-generated bundle id.)

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Hall via wix-devs
Sent: Tuesday, 15 December, 2020 16:12
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Hall <r.sean.hall at gmail.com>
Subject: [wix-devs] 4991 - Handling of related bundles missing from cache

I created a WIP for 4991 at
https://wixtoolset.org/development/wips/4991-handling-of-related-bundles-missing-from-cache.
Any feedback?
____________________________________________________________________
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/