Summary
This article explains how to add file types other than portable executables (EXE, DLL, OCX, etc.) to your project so that a separate component is created and it is marked as a key file.Synopsis
This article explains how to add file types other than portable executables (EXE, DLL, OCX, etc.) to your project so that a separate component is created and it is marked as a key file.
Discussion
Microsoft Best Practices state that each portable executable file (EXE, DLL, OCX, etc.) should have its own unique component and be marked as a key file. This allows for these files to be repaired or upgraded in the future. This option can be selected when using the New Component Wizard, or directly from the Files and Folders view:
- Select the Application Data > Files and Folders view.
- Right-click on "Destination Computer" in the middle lower panel and choose "Show Components".
- When files are added via drag & drop, new Components are created for them using Best Practices.
However, at times you may wish to follow these Best Practices for other file types as well (TXT, ZIP, JAR, etc.). To modify these settings, follow the steps below:
- Open the Registry Editor (regedit.exe) and browse to this key:
HKEY_CURRENT_USER\Software\InstallShield\<version>\Professional\Project Settings
- Create a string value named "PEFileExtensions".
- Set it's value date to "EXE|DLL|OCX|VXD|CHM|HLP|TLB|AX|MYFILEEXTENSION"
It's necessary to include at least these values EXE|DLL|OCX|VXD|CHM|HLP|TLB|AX, but then you can simply append any additional file extensions you'd like to have this same behavior.
Related Articles
Known Issue: Usage is not tracked for executable files in the installation directory of a Windows Installer package that a… 14Number of Views Create local file evidence in Flexera One ITAM or FlexNet Manager Suite 53Number of Views Capture web session traffic in a HAR file for troubleshooting 444Number of Views Create a Windows Registry Entry with Type REG_NONE for Windows File Type Association 6Number of Views CAB file extraction during ARL/batch data import operations may fail with "cannot create file" errors due to file locking 3Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago