Reply to Thread

Re: Releases and Differing Sets of Files

Hi Friedrich, it does help, but probably not the way you think.

It inexplicably did not occur to me that a "Does not equal" option would exist on compiler directive "if" statements like it does on regular "if" statements.

Duh, thanks.

As I mentioned, though, I knew that I could do what I was looking to do in the script (somehow) but preferred a Visualizer-based option, for consistency's sake.

So, please consider this enhancement request: To include a "Releases" drop-down list box on the "Conditions" tab of the "Files and Directories" properties dialog.

Thanks,

Wayne

Re: Releases and Differing Sets of Files

Wayne,

You have several different options. Each "Release" can have a different set of compiler variables. Based on this, you can generate completely different sets of outputs.

The following is the easiest way:

[ Install Files ]
#ifcompvar [SB_RELEASEID] Does Not Equal (Ignore Case) "ComposerDownloadTrialWithoutHelp" Then
Install File "C:\Composer\Composer.chm" to "%_SB_INSTALLDIR%\Composer.chm" (Always Install)
#end

If the selected Release is "ComposerDownloadTrialWithoutHelp", then Composer.chm is not compiled into the install.

Does this help?

Friedrich

Releases and Differing Sets of Files

Hi,

I feel like I'm overlooking something obvious.

Using the example in the Help under "Releases", there's a "ComposerFull" release and a "ComposerDownloadTrialWithoutHelp" release. This implies that "ComposerFull", which let's say is the default, includes a file called "Composer.chm" and the "ComposerDownloadTrialWithoutHelp" doesn't.

The help doesn't quite go so far as to explain how to accomplish including or not including "Composer.chm" in the installation.

So, using the "Files and Folders" visualizer, is there a way I can tell SB7 to not include "Composer.chm" when the release is set to "ComposerDownloadTrialWithoutHelp"? It seems like that should be on the "Conditions" tab of the File Details.

I know I can do this in script, but even then, given the scenario I've laid out where a file is already being installed in the default release, it would be awkward to use script code to somehow de-install it. It would be nice to see all the files to be installed in the "Files and Folders" and be able to see in each one's details which release it's included in.

Thanks,

Wayne