Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Burn bundle caching issue #4324

Closed
wixbot opened this issue Feb 24, 2014 · 1 comment
Closed

Burn bundle caching issue #4324

wixbot opened this issue Feb 24, 2014 · 1 comment
Milestone

Comments

@wixbot
Copy link

wixbot commented Feb 24, 2014

Guess We have bundle Setup.exe that authors Package1.msi and Package2.msi. We also have a patch bundle Patch.exe with Patch1.msp for Package1.msi.
Try to install Setup.exe with Package2.msi only. Then install Patch.exe. Patch1.msp will not be cached (It seems like Burn didn't found related Package1.msi installed and refused to cache Patch1.msp). Now try to run modify operation of Setup.exe and select Package1.msi for install. Burn runs related Patch.exe during installation and it fails to install Patch1.msp for Package1.msi because it wasn't previously cached. It also cannot show "find source" dialog because of silent mode. Finally, entire bundle fails to run modify operation.

Originally opened by vitaly

@wixbot
Copy link
Author

wixbot commented Feb 27, 2014

This is two feature requests: http://wixtoolset.org/issues/4329/ and http://wixtoolset.org/issues/4330/.

Resolution set to accepted
Status changed from Untriaged to Resolved

@wixbot wixbot added this to the v3.8 milestone Dec 20, 2015
@wixbot wixbot closed this as completed Dec 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant