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
- :
- Re: Component Files Help
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
‎Dec 22, 2008
04:48 PM
Component Files Help
We have multiple machines and multiple staff that need to all work on the same projects from time to time. We're going to be storing our project files in SourceSafe in the future. This will allow us to share project files easily enough but we have one issue with doing this. Our machines are not all configured with the same disk partitioning scheme. As a result, we do not all share a common directory for included component files. For example, I house my EXEs, DLLs, etc. on drive C: while other staff use D:.
Is there a way to define an environment variable or IS setting that will allow me to tell IS to grab included files from C:\Directory on one machine but use D:\Directory on another machine?
We're not talking about IS script files and such. We are talking strictly about the files included in the components/features when we build our installer (files being prepared for deploy at client sites).
Is there a way to define an environment variable or IS setting that will allow me to tell IS to grab included files from C:\Directory on one machine but use D:\Directory on another machine?
We're not talking about IS script files and such. We are talking strictly about the files included in the components/features when we build our installer (files being prepared for deploy at client sites).
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
04:56 PM
Look at Path Variables. They can be Standard (edited by the developer in the project settings), or defined by either Environment variables or Registry values.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 22, 2008
06:37 PM
Bingo! Took me a little while to figure out what I was doing wrong with my Path Variable definition but I got it worked out. As I was reading through the documentation I kept seeing which is what I kept trying to use. I took the <> off in my "Defined Value" column and it finally started to work for me.