I expect it’s by design since pulling the source out from under an MSI that was
delivered by a bundle leaves the user in a bad place if they ever need the
source again.
Of course, it almost guarantees the MSI source is “leaked” in the cache.
There is no great answer here (unless we started teaching MSIs how to clean
their own cache… which is interesting but terrifying at the same time).
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Sean Hall [mailto:r.sean.h...@gmail.com]
Sent: Sunday, March 1, 2015 12:18 PM
To: WiX toolset developer mailing list
Subject: [WiX-devs] Burn caching behavior during uninstall
When a BA plans and applies the Uninstall action, but requests its packages to
be Present, the packages are not cleaned from the package cache. Is this by
design, or a bug?
Detect begin, 1 packages
Detected package: Test.msi, state: Present, cached: Complete
Detect complete, result: 0x0
Plan begin, 1 packages, action: Uninstall
Planned package: Test.msi, state: Present, default requested: Absent, ba
requested: Present, execute: None, rollback: None, cache: No, uncache: No,
dependency: Unregister
Plan complete, result: 0x0
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
