| || |
Unrestricted access to Windows Installer functionality!
| || |
Plain XML based source scripts!
| || |
Free, no strings attached!
| || |
Command-line interface for automated application build process!
| || |
Thriving community support!
What does ICE91 check?
ICE91 checks if a file, .ini file, or shortcut file is installed into a per-user only directory. ICE91 warnings are harmless if the package is only used for per-user installations and never used for per-machine installations.
Files, .ini files, or shortcuts in per-user only directories are installed into a particular user's profile. Even if the user sets the ALLUSERS property for a per-machine installation, files, .ini files, or shortcuts in per-user only directories are not copied in to the "All Users" profile and are not available to other users. The per-user only directories do not vary with the ALLUSERS property. The following is a list of the per-user only directories:
Note: The ALLUSERS property determines where the configuration information of the installed application is stored (per-user versus per-machine). If ALLUSERS is not set, the installer does a per-user installation.
If a file or .ini file, or shortcut is set to be installed to the per user directory that doesn't vary based on ALLUSERS value, this specific resource won't be copied to each user's profile even if a per machine installation is desired.
When does ICE91 show up?
ICE91 posts a warning if a file, .ini file, or shortcut file is installed into a per-user only directory.
How can I fix ICE91?
ICE 91 warning message means that the MSI will only install the resource into the user profile for the user account that executes the MSI, but not for any other user accounts on the same machine.
As far as the application functionality is concerned, check to see if it is a necessity that the resource be copied into each user’s profile for correct functionality of the application or not. If the resource does not need to be in the user profile to work (i.e., it might work in a folder under All Users profile) then install it to a folder under All Users profile.
If the resource must be copied to each user’s profile, then add functionality to your package to do this. To achieve this, add a current user registry key (i.e., just a dummy registry key) and make this registry key the key path of the component which contains the resource. This means that the resource will be copied to the next user’s profile as part of the MSI self healing mechanism, provided that advertised entry points exist for the product.