This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Suite Package items I ran across
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2011
06:01 AM
Suite Package items I ran across
1. As I mentioned before, it would be nice to migrate a Primary display box to a secondary option. I did the work around but it would be nice to use the primary display box's features on the secondary. Items to use would be the buttons.
2. When switching out the EULA. it will bring our EULA in place, but the Print button still references the places holder. If you name yours the same it works but since I have two EULA we are working with they are different names.
3. When adding a Browse Dialog box window and associating to a package, it creates a property to pass into the package for INSTALLDIR. This property is mixed case and I was wondering if there will be an issue running in silent mode since it is not upper case?
Attached is a copy of my current project.
What do we need to do to build this via Stand Alone Builder? Is this linked via the Automation DLL?
2. When switching out the EULA. it will bring our EULA in place, but the Print button still references the places holder. If you name yours the same it works but since I have two EULA we are working with they are different names.
3. When adding a Browse Dialog box window and associating to a package, it creates a property to pass into the package for INSTALLDIR. This property is mixed case and I was wondering if there will be an issue running in silent mode since it is not upper case?
Attached is a copy of my current project.
What do we need to do to build this via Stand Alone Builder? Is this linked via the Automation DLL?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 16, 2011
09:01 AM
On our media we have a set of files for personel to link to to review files. Right now I added to the Support Folder under the Language folder, which will place the files down into the Temp location 1033 location. I link to this folder and it works fine, but we really want to have the files exist on the media where they are running the install from. Is there a way in the build of the suite to copy the file/folders onto the media so we can link against them?
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)