Installer Version 5.0 in Windows 7
Windows Installer version 5.0 is included in Windows 7 Beta. The MSDN documentation section has been updated accordingly and available for online viewing. The most significant properties being.
MSIFASTINSTALL
This property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation. The value of the MSIFASTINSTALL property can be a combination of the following values.
| Value | Meaning |
| 0 | Default value |
| 1 | No system restore point is saved for this installation. |
| 2 | Perform only File Costing and skip checking other costs. |
| 4 | Reduce the frequency of progress messages. |
MSIINSTALLPERUSER
This property requests that the Windows Installer install the package only for the current user. To use this option, the package has to have been authored to be capable of a per-user installation.
If ALLUSERS=2, the installer always resets the ALLUSERS property to an empty string ("") or 1 based on whether it determines to do a Per-User Installation or a Per-Machine Installation.
If the ALLUSERS property is set to 2 and MSIINSTALLPERUSER is set to an empty string (""), the Windows Installer requests a per-machine installation.
If the ALLUSERS property is set to 2 and MSIINSTALLPERUSER is set to 1, the Windows Installer requests a per-user installation.
Windows Installer ignores the value of the MSIINSTALLPERUSER property in the package or on the command line during the repair of an installed package.
Windows Installer 4.5 or earlier: Not supported. This property is available beginning with Windows Installer 5.0.
In addition, all functionality provided with the MSI 4.5 redistributable release is included on Windows 7.
Do look into this below link for more information.
http://msdn.microsoft.com/en-us/library/dd408114(VS.85).aspx
In addition
One other change is that the locally cached MSI will retain any internal CAB files, to get around the current problem where the uninstall reports an unsigned MSI (because removal of internal CABS invalidates the code signing)
Any MSI files with external CABS will only cache the MSI as now.
Even if the entire MSI is cached locally, it will still not be recorded as the source location.
Authors of large MSI installations should therefore consider whether to always keep their CAB files external to the MSI to avoid cluttering up the local cache on workstations. Although hard disks are getting bigger, it is wasteful to cache an entire large application due to it having internal CABs
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
Would you like to reply?
Login or Register to post your comment.