Click or drag to resize

Using the Setup Designer

Nimbus provides a Driver Setup Designer for customizing the driver installer without directly editing the WiX source files. The designer automates some of the more common driver installer customization tasks. For instance, adding a set of example programs can easily be done with the Setup Designer.

The Setup Designer is accessed via the Setup Designer node in Solution Explorer. The designer presents a tree view in the left pane representing the set of folders on the target machine. The grid view in the right pane displays the items the installer will deploy in the folder selected in the tree view.

Many of the folders in the tree view are shown in gray. These folders cannot be edited as most are part of the standard IVI folder structure, which can only be modified by the IVI Shared Component installer -- not by IVI driver installers.

The Setup Designer only modifies the Setup.wxs file within the driver setup project. Other required WiX source files are also present within the Internal project folder, but the Setup Designer only reads those files.

Caution note Caution

Although Visual Studio will allow you to easily view and modify WiX source files (.wxs and .wxl) directly, doing so is an advanced operation and should be done with great care to make sure your solution is checked in under a source code control system, or you have backed up the WiX source files before manually modifying them.

The following types of customizations can be performed with the Setup Designer. More advanced customizations might require directly editing the other setup project files, such as the Setup.wxs. The topic Learning More about WiX provides useful links to WiX resources for understanding how to work with WiX installers.

To add a single file or flat list of files to be installed on the target machine

  1. Right-click on one of the editable folders in the tree view. Often, the only folders to which files may be added are the driver's own folders -- named <driverName> and shown in bold.

  2. Choose Add Files.

  3. The standard Windows Add Files dialog appears.

  4. Choose the files to be added and click Open.

  5. The Setup Designer displays the added files in the right-side grid view.

To add a hierarchy of files and folders to be installed on the target machine

  1. Right-click on one of the editable folders in the tree view under. Often, the only folders to which files may be added are the driver's own folders -- named <driverName> and shown in bold.

  2. Choose Add Folder.

  3. The standard Windows folder browse dialog appears.

  4. Choose the root folder of the items to be added and click OK.

  5. A special dialog appears showing a flattened list of the files that will be added. Note that even though the list is displayed as a flat list of files, the Setup Designer will preserve the actual hierarchy when the files are actually added.

  6. Use the check boxes next to each file in the list to include or exclude individual files. The Exclude text box near the bottom of the dialog can be used to filter out files based on file extension.

  7. Once the desired set of files are checked, click OK.

  8. The Setup Designer displays the added folders in the tree view on the left along with the contents of the selected folder in the grid view on the right.

To add items to the Start Menu

  1. Right-click on a folder in the tree view on the left or on a file in the grid view on the right.

  2. Choose Create Shortcut to ....

  3. The Setup Designer creates a shortcut to the specified folder or file.

  4. Drag and drop the shortcut to the desired location under the Start Menu.

To add one or more .NET assemblies to the GAC

  1. Right-click on the Global Assembly Cache node in the tree view.

  2. Choose Add Files.

  3. The standard Windows Add Files dialog appears. Note that only .NET assemblies can be added to the GAC.

  4. Choose the files to be added and click Open.

  5. The Setup Designer displays the added files in the right-side grid view.

See Also

Download a complete CHM version of this documentation here.