Customize the location uncompressing the xxxxx.tmp file ?

[Umberto Colapicchioni]

I'm asking this, because if the setup needs to download something ( using IDP plugin, for example ), since it's being executed from the %TEMP% folder as a setup.TMP file, it makes difficult to create a firewall exception for it to allow it to proceed with the download, since the path to the executable will always be different at every startup.

I understand this might be fixed by setting UseSetupLdr to No, but that would result in multiple files being created and I need to use SIgnTool to sign the setup, so that's not an option.

Is it possible to specify a fixed custom location to decompress the setup ?

[Gavin Lambert]

On 11/10/2022 00:16, Umberto Colapicchioni wrote:
> I'm asking this, because if the setup needs to download something (
> using IDP plugin, for example ), since it's being executed from the
> %TEMP% folder as a setup.TMP file, it makes difficult to create a
> firewall exception for it to allow it to proceed with the download,
> since the path to the executable will always be different at every startup.

Firewalls are not typically configured to prevent outgoing connections,
which is what that is. So usually no firewall changes are needed.

> Is it possible to specify a fixed custom location to decompress the setup ?

There is not currently any option for that.

[Umberto Colapicchioni]

Firewalls are not typically configured to prevent outgoing connections,
which is what that is. So usually no firewall changes are needed.

Sure, but some users of our product said they configured the firewall to be more restrictive, and they are complaining our software is at fault, because by uncompressing itself each time in a different random folder, it makes impossible for them to create a firewall rule that will allow to download whatever it needs to download when it starts.

Users being users, they claim ours is the "only" installer in the world that has this "problem", when of course uncompressing in a random folder is the standard for installers so, I guess with the firewall configured that way, they would have the same issues with any other installer that downloads something.

 

There is not currently any option for that.

Too bad, but I understand it was a fringe case.

 

[David Hollman]

One suggestion is to install a separate program which will perform the download. It could go into a standard location with a standard name. And then your installer can delete it when it is finished.

Another approach would be to perform whatever the download is before building your installer, though that may not meet your requirements.