Hello,
I'm using the bootstrapper to deploy a 32/64 (En,DE) mixed installation (all files included in the exe).Everything works fine but I have some doubts. I have problems by changing/reparing an installation, when the exe (bootstrapper) is no more on the folder from where the installation was started. I have made some tests and got the following results as well as questions:
1.- In case the Bootstrapper options (Media) "Do not delete extracted MSI and CAB files" is unchecked (Default):
a) Unpacking: the unpacking process works fine. If one cancel the installation the files are also deleted as a part of the rollback process (cool).
b) Installing: the installation process works also fine. After finishing the installation process, the unpacked files are also deleted.
c) The Problem: Let say a user load my exe from the web, he copies it on the desktop and install it. Afterwards he deletes the file and some time after he try to change/repare the installation, by clicking the "modify" button on the Software list from Windows. At this point, the installation wants to have the path to the unpack folder, not letting the user to modify/repare.
Even worse (in my personal case. It happenned one time and I couldn't reproduce this again), cancelling this "Browse folder" dialog can make the installation process end with an error, avoid to deinstall the applciation, even if the files are located where they were.
2.- In case the Bootstrapper options (Media) "Do not delete extracted MSI and CAB files" is checked:
a) Unpacking: the unpacking works fine.
b) Installing: The installation woks fine. changing/reparing the instalaltion without having the initial exe works too. The unpacked files are deleted after uninstall, what I find perfect.
c) The Problem: Different than in Point 1-a, if one cancel the installation, the unpacked files remain on the computer. Since the installation was aborted I would expect that those files are deleted as a part of the rollback process. Is this a bug? or do I'm missing something here?
3.- About the C:\Windows\Installer folder:
- Other installation tools that I have seen (or Windows MSI itself, I'm not sure) create automatically a copy of the actual launched and installed MSI file on C:\Windows\Installer. This installation copy will then be called from MSI, for any change needed to do to the installation.
- Example: I have an installation (written with Wise Installation Studio 7) that uses also a kind of bootstrapper (but somehow separed of the "Media" part of the installation). This exe also extract the files to a temp folder, apply a transform to an msi, install the application and copy that msi to the Windows/installer folder. So can the user always repare/change the instalaltion, without having the original exe.
- The Problem: In case of Advanced-Installer will only a msi file created and copied to C:\Windows\Installer, which is a kind of link to the exe.... if the exe is removed from its initial location, neither modify nor repaair nor deinstall will work. Can I change this behavior to work like the example described above? Do I have anything wrongly configured?
Thanks in advance,
Keneth
FOLLOW US
Get the latest news in Application Packaging