Hi,
The solution that Cosmin gave causes an empty folder to be installed if no applications are installed.
We will work on a solution for the behavior you encountered, but for now I'm afraid that this is the only workaround for hiding the text shown during Maintenance.
I did not have this problem with the old installer built with InstallShield.
Did you by any chance use the same folder structure (no files in the main installation folder, only sub-folders)? If this is the case can you please provide an URL from where we can download the package? It would mean a lot to us and it will help us greatly in finding a solution.
Unfortunately this is a Windows Installer problem and we need to find a workaround for it (if there was a problem in Advanced Installer we could have easily fixed it). The
Feature table inside the MSI contains the "Directory_" column which contains the name of the installation folder of the feature. If no file is installed in this folder, then Windows Installer won't know that the feature was installed in it. Therefore, during Maintenance the default path of the folder will be used and this path will be shown.
I noted that the installation folder is, in fact, saved in the registry, so it is available during maintenance.
Yes, this is true, the installation folder is saved in the registry automatically by Windows Installer. However, we did not make Advanced Installer get this path during Maintenance because we never through it was needed (like I said before, we overlooked the situation you encountered). Under normal circumstances, Windows Installer will resolve the path automatically.
Please note that the installation folder can be retrieved during Maintenance by following these steps:
- go to the
Registry page and create a new registry value
- use
[ProductCode] as the name of the value and set the "Data" field to
[APPDIR]
- go to the
Search page and create a search for this registry value
- name this search
APPDIR
With this approach the package will retrieve the installation path from the registry (if it exists). Also, since this approach will set the correct installation path during Maintenance, you no longer need to create the installation folder on the target machine. However, the installation path will be shown during Maintenance.
In my opinion, a solution would be to place another Uninstall shortcut in the installation folder. This way, the folder will not be empty if no applications are installed.
Advanced Installer uses a bunch of custom actions in the UI sequence and I believe one or more of these is causing the problem.
I'm afraid that this is not the case. We acknowledge bugs, we fix every bug reported by our users and we would have fixed this if it was an Advanced Installer bug. Unfortunately, the only solution for us is to find a workaround for the Windows Installer behavior and try to find a better implementation of the involved Advanced Installer features.
I may need to ditch Advanced Installer in favour of another installer that does not hide a lot of important information from the installer builder.
Please note that the internal custom actions used by Advanced Installer ensure that the packages are created correctly. If these custom actions were exposed and you could modify them, the resulted MSI package may not work.
We apologize for any inconveniences caused by Advanced Installer and we hope we can offer better solutions in the future.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging