Settings > Designing > Naming Convention

The naming convention options deal with the following topics in the pack designer:

•Features

•Components

•Create and remove entries

•Drivers

Click on the individual items to view more information.

Features

This section deals with the naming and description of the main feature of any MSI / RPP based packages / projects.

Default name:

This is the display name shown in any UI. This value is used to populate the Feature table 'Title' column. See the MSDN MSI online documentation for more information.

Default description:

This is the description of the feature shown in any UI. This value is used to populate the Feature table 'Description' column. See the MSDN MSI online documentation for more information.

Components

This section deals with the naming of the components for none executable files (exe, ocx, dll, sys) in MSI / RPP based packages.

Default name of components without PE-executables:

This is the suffix added to a components that contains non executable files. The @ character is replaced with the name of the directory in which the resources of the component (in this case files) are installed to.

Create and Remove Entries

This section deals with the creation of empty directories and the removal of files and directories in MSI / RPP based packages.

Default name of CreateFolder entry:

Whenever a CreateFolder table row is created, RayPack uses this default value to automatically determine a decent data object reference.

See the MSDN MSI online documentation for more information regarding the CreateFolder table.

Default name of RemoveFile entry:

Whenever a RemoveFile table row is created, RayPack uses this default value to automatically determine a decent data object reference.

See the MSDN MSI online documentation for more information regarding the RemoveFile table.

Drivers

Feature name:

Whenever drivers are added to a packaging project, RayPack automatically creates a new feature for storing driver information. Please make sure to use a name that is informative and suitable for swift orientation within the potentially large amount of features within a project. This makes it easier to identify drivers and install drivers correctly using the DIFxApp (Driver Install Frameworks for Applications) methodology.