Standard Properties
Previous Topic  Next Topic 

Some properties are standard to many objects throughout InstallJammer.  This is a list of standard properties that can appear throughout your project and what they are.  An object is defined as any piece of an install (file group, file, action, condition, etc...).


A unique identifier for this object.  This ID is generated when the object is created and does not change throughout the life of the object.


This property tells you what component was originally used to create this object.


This tells InstallJammer whether this object is active or not.  An inactive object is not packaged when building an installer.


An alias is an alias by which to call an object ID.  Any object in InstallJammer that has an ID can also have an alias.  This makes it easier to remember objects by their alias instead of their object ID.  For example, the Install Actions group that is created for a new project is aliased to be called Install Actions to make it easier to call from other actions.



Comments are sometimes provided by InstallJammer to tell you what an object is doing, but they are usually set by someone building the project.  Comments are not used by InstallJammer for anything and can contain any text you want.


This tells you if there are any conditions placed on the object that will be checked during installation.  Selecting this property will let you bring up the Conditions Editor to see and modify any conditions on the object.


This property is used to hold user-specific data.  Just like comments, this data is not used by InstallJammer and is safe for you to store anything you want into it.  This can be helpful for storing other bits of relevant data with an object in the system for use by other objects, actions or conditions.


This property tells InstallJammer when and where to include this object when running an installer or uninstaller.  The object will either be: always included, included only when testing or included only when not testing.  This property is affected by the <%Testing%> virtual text.  When testing, only objects which are always included or included when testing will be created.  When not testing, only objects which are always included or included when not testing will be created.