2 replies to this topic

[thetamind]

I am setting up a InstallShield 10.5 project with multiple project release configurations. Each configuration has the same binary executable files but different configurations, registry, etc.

I have a file containing sensitive information that needs to be installed in one configuration but have an empty file installed in the other configuration. I need the sensitive file to not be distributed in the setup.exe release that will only install the blank file.

Is there a way to selectively include and exclude files packaged in the setup.exe during the build process?

Thanks for your help.

[Stefan Krueger]

In my understanding, if the file is excluded by your release flags, it shouldn't end up in the install package. Does this not work for you?

[thetamind]

Thanks for pointing me in the right direction. After reading some documentation about release flags I now know what they are used for. Indeed files are not included in the package when the associated feature is disabled.

Thanks for your help.