- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Custom prerequisites source directory
- 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
Custom prerequisites source directory
What is the purpose of the ISSetupLocation column in the ISSetupPrerequisites table? I can't seem to find any documentation on it.
I'm looking for a way to pull setup prerequisites from a custom external directory -- one that is not "ISSetupPrerequisites" as an immediate subdirectory. Any help is appreciated.
Thanks.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
The link provided in 2010 by MichaelU is understandably dead but looking at this now I'm still curious about this column and wanting to accomplish a similar thing to twinsky. ISSetupLocation sounds like where I might put a custom path to the prerequisite location but it's apparently a short integer so I'm wondering if it gives a number reference to a series of locations and I write the actual file path somewhere else?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @jcomish,
Thank you for your post.
Are you referring to specifying the source location for prerequisites at design-time? Or at build-time?
If so, please review the documentation at the following link:
https://docs.revenera.com/installshield28helplib/helplibrary/UpgrdngToIS2011.htm
specifically, the "Changing Design-Time and Build-Time Locations of Existing InstallShield Prerequisites in Existing Projects" Section, for more information.
ISSetupLocation is mostly a red herring. I believe ISSetupLocation determines whether the prerequisite gets packed into the setup.exe, etc. And, I'm fairly certain that ISSetupLocation is an enum, not a short integer.
Please give these suggestions a try. Do they work for you?
Hope this helps.
Please let us know if you have any questions or concerns. Thanks!