Skip to content

Customizing a component type for the runtime component

The runtime files are mostly binary encrypted due to compilation. They cannot be compared directly with the data of the editor component. It is therefore advisable to create a separate runtime component for a targeted comparison, as described below.

Procedure

  1. Create a Runtime component type in the Component type editor module of the AdminClient.

  2. In the Compare these files area, enter all files that are to be taken into account in a comparison.

    Info

    Entry *.*, Comparator: Binary, Subdirectory: Include.

    Examples of file extensions often contained in the runtime files:

    Specification Comparator Subdirectories
    *.txt ASCII Include
    *.ini ASCII Include
    *.xml ASCII Include
    *.pdf PDF Include
    *.wsp6 ASCII optional

    In the Ignore these files during the comparison section, you can exclude files and folders that interfere with the comparison or are unimportant.

    Examples of files that change simply by recompiling:

    Specification Subdirectories
    Project.cmp Include
    VBR_Para.ems Include

    Examples of runtime files that change just by activating the runtime:

    Specification Subdirectories
    Project_m.vba Include
    VSTAorig.zip Include

    In the Save these files and Ignore these files sections, you can specify which files from the working directory are saved.