Resolving Design-Time Conflicts While Importing a DIM Into a Basic MSI Project

InstallShield 2016

Project • This information applies to Basic MSI projects.

When you import a DIM project into an installation project, InstallShield merges the DIM data into the installation project. If data conflicts exist, InstallShield needs to determine which data takes precedence: the values in the DIM project or those in the Basic MSI project.

InstallShield lets you specify how you want to resolve conflicts between settings in the two projects when you are importing. Following are examples of different types of conflicts that may occur:

If InstallShield encounters a conflict when importing a DIM project, the Resolve Conflict dialog box opens. This dialog box is where you specify how you want to proceed. To learn more, see Resolve Conflict Dialog Box.

In most cases, conflicts do not occur, since InstallShield automatically includes a DIM project–specific GUID in the names of items such as properties, string entries, path variables, and components when you create these in a DIM project, but not in a Basic MSI project. If you create a property called MYPROPERTY in a Basic MSI project, the property is called MYPROPERTY. If you create a property called MYPROPERTY in a DIM project, InstallShield internally calls the property MYPROPERTY.DIM_GUID, where DIM_GUID is the identifier that is defined in the DIM GUID setting of the General Information view of the DIM project. Thus, the name of the property in the DIM becomes, for example, MYPROPERTY.8356F8B7_8DE5_4E04_A77A_6FA722CBE1CC. For this particular example, you can use the Direct Editor to see the internal name of the property in the Property table of the DIM project.

See Also

Importing a DIM into a Project

Import DIM Wizard

Open topic with navigation