Wrong or Incorrectly Disabled File Names Displayed in LabVIEW 8.5 Installer Builder
Primary Software: LabVIEW Development Systems>>Professional Development System
Primary Software Version: 8.5
Primary Software Fixed Version: N/A
Secondary Software: N/A
Problem: When building an installer for my LabVIEW built application, filenames appear disabled, duplicated, or incorrect in the
Installer Properties dialog box. This impairs my ability to create installers that include shortcuts to additionally included files, automatically register COM components, or contain LabVIEW classes.
Solution:
The filename issue stems from a couple of distinct bugs in LabVIEW 8.5. The problems manifest themselves in a few similar ways in the
Installer Properties dialog box:
- When adding files from the Project View to the Destination View to include additional files with the installer, the files in the Destination View can appear with duplicate or incorrect file names. This occurs both with LabVIEW classes as well as with other file types which were included in the application's build specification.
- On the Source File Settings page, when selecting files you want to register as COM objects after the installer runs, the
Register COM checkbox might be incorrectly enabled/disabled for chosen files..
- When creating additional shortcuts from the Shortcuts page, the names of items might appear incorrect. If items
are selected, incorrect shortcuts are created.
The workarounds for these issues depend on which exact issue you are experiencing.
If you are having problems building an application with LabVIEW classes due to incorrect filenames appearing in the
Destination View, you will need to make changes to the application's build specification (as opposed to the installer specification). Make the following changes to the build specification to resolve the problems:
- Open the application's build specification and navigate to the Destinations page.
- Add a new destination for each class that includes duplicate file names (override VIs).
- Go to the Source File Settings page and configure each class (and its files) to go to a unique destination.
- Rebuild the application and reconfigure the installer build. You will only need to complete this process one time.
To fix the other issues, you will need to make changes to both your application's build specification and installer specification. In the case of adding shortucts, or registering COM objects, you can work around the problem by removing these files from the
Always Include section of your build
specification, and instead add them from the
Source Files page of the installer build. This work around creates an incomplete
application since you may be excluding files needed by the application in the application's build specification. The excluded files are then included by the installer so that when installing your application, all files are placed on the target computer correctly. Because you may need to distribute your application without an installer, National Instruments recommends making a new build specification for this workaround. By having the two specifications, you will easily be able to create a complete application as well as a complete installer for the program.
Related Links:
Attachments:
Report Date: 10/17/2007
Last Updated: 10/18/2007
Document ID: 4EGEL6HY
