Click to Rate and Give Feedback
MSDN
MSDN Library
Windows Development
Windows Installer
Properties
About Properties
 Public Properties
Public Properties

Public properties can be authored into the installation database in the same way as private properties. In addition, the values of public properties can be changed by a user or system administrator by setting the property on the command line, by applying a transform, or by interacting with an authored user interface. Public property names cannot contain lowercase letters. See Restrictions on Property Names.

Public properties are commonly set by users during the installation. For example, the public property INSTALLLEVEL property can be specified at the command line used to launch the installation or chosen by using an authored user interface.

Public property values can be overridden either at a command line, by using a standard or custom action, by applying a transform, or by having the user interact with an authored user interface. To clear a public property in the property table, leave it out of the table. Properties that are to be set by the user interface during the installation and then passed to the execution phase of the installation must be public.

For a list of the standard public properties used by the installer see Property Reference. An author can also define a custom public property by entering the property's name and an initial value into the Property table. All public properties can be overridden by all users if any of the following conditions are true.

  • The user is a system administrator.
  • The per-machine EnableUserControl policy is set to 1. See System Policy.
  • The EnableUserControl property is set to 1.
  • This is an unmanaged installation that is not being done with elevated privileges.

If none of the above conditions are true, the installer defaults to limiting which public properties can be overridden by a user that is not a system administrator. See Restricted Public Properties.

 

 

Send comments about this topic to Microsoft

Build date: 9/7/2011

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Don't forget to consider SecureCustomProperties, AdminProperties, and MsiHiddenProperties      Robert Flaming - MSFT   |   Edit   |   Show History

The Property table is one of those tables that does not have an attribute column rather it uses another property containing a semicolon delimited list of other property names.

The ones most folks need to watch for are SecureCustomProperties, AdminProperties, and MsiHiddenProperties.

Probably would have made more sense to have these as attributes but this is a very old design.

====================================


Robert Flaming
Windows Installer Program Manager
Team Blog: http://blogs.msdn.com/windows_installer_team
Own Blog: http://blogs.msdn.com/rflaming

All postings are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm


Processing
© 2012 Microsoft. All rights reserved. Terms of Use | Trademarks | Privacy Statement
Page view tracker