Suite package uninstallation fails if not cached locally
I have found that uninstalling my suite consistently fails if I do not choose to 'Cache Packages Locally' for my release. Looking at the debug log, I see the following:
10-21-2011[01:33:15 PM]: Will launch exe: C:\Users\FAROAD~1\AppData\Local\Temp\{06A2AB7C-FC01-4ABC-87B7-D1198C3ECDA7}\{925759E8-0010-40E3-9F7C-0E474D141698}\setup.exe 10-21-2011[01:33:15 PM]: Parcel target exe does not exist 10-21-2011[01:33:15 PM]: Parcel operation return status: 80070002
And in fact this path does not exist during the uninstall operation since I am not caching the packages. I would think that if the packages aren't cached, that they would be run from the source location. This is easily remedied by caching the packages, but then why have the option?
Often a package will cache its own uninstallation-only executable somewhere. An MSI package does this with msiexec.exe and the cached .msi file beneath the windows folder. But in the case of an EXE package, it's your job to point us to that uninstall. If you instead want to run the original installation executable (which may have include the uninstallation capability), it generally needs to be cached.
