Skip to main content

ADDLOCAL & ADDSOURCE Properties

ADDLOCAL property

The value of the ADDLOCAL property is a list of features that are delimited by commas, and are to be installed locally. The features must be present in the Feature column of the Feature Table. To install all features locally, use ADDLOCAL=ALL on the command line.
Do not enter ADDLOCAL=ALL into the Property Table, because this generates a locally installed package that cannot be correctly removed.
Do not use spaces between names. Use the format ADDLOCAL=value,value,value...


ADDSOURCE property

The value of the ADDSOURCE property is a list of features that are delimited by commas, and are to be installed to run from the source. The features must be present in the Feature column of the Feature Table. To install all features as run from source, use ADDSOURCE=ALL on the command line.
Do not enter ADDSOURCE=ALL into the Property Table, because this generates a run-from-source package that cannot be correctly removed.

Remarks

The feature names are case sensitive.
For example:
      If the command line specifies: ADDLOCAL=ALL, ADDSOURCE = MyFeature, all the features are first set to run-local and then MyFeature is set to run-from-source.
      If the command line is: ADDSOURCE=ALL, ADDLOCAL=MyFeature, first MyFeature is set to run-local, and then when ADDSOURCE=ALL is evaluated, all features (including MyFeature) are reset to run-from-source.

This means ADDSOURCE is superior to ADDLOCAL, in terms of implementation.



Detailed difference between addsource and addlocal.

On Windows 7, the ability to run as “Per-User”
      All files are installed to Per-User folders, such as “C:\Users\$User\AppData\Roaming” on Windows 7
      All Shortcuts and the Add/Remove Control Panel entry are only seen by that user
      All registry entries (Application data and registration) are made to HKEY_CURRENT_USER hive.
      No registry entries are made to machine-wide registry keys, such as HKEY_LOCAL_MACHINE or HKEY_CLASSES_ROOT hives
      The installation package cannot allow the user performing the installation package to select destination directories that are machine-wide, such as “c:\Program Files” All application binary file (EXE, DLL) need to be digitally signed to be allowed to be installed by “Per-User” for Windows 7.


On Windows 7, if any of the above constraints are not met, the package will be installed “Per-Machine” – this means that a “Per-User” will not be allowed!

Comments