[wix-users] How do I handle SetupFilesCleanup and SetupFiles Extract in Wix
henderso at opentext.com
Fri Sep 2 06:03:49 PDT 2016
I'm still learning WiX, but doesn't the CustomAction at BinaryKey along with the Binary at SourceFile accomplish this? The Binary at SourceFile specifies a .dll (or .exe?) that is used by the custom action, but it's not one of the permanently installed files. It's automatically extracted by the MSI, used, and then deleted when the MSI is done with it.
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Tobias S
Sent: Friday, September 2, 2016 4:32 AM
To: WiX Toolset Users Mailing List <wix-users at lists.wixtoolset.org>
Subject: Re: [wix-users] How do I handle SetupFilesCleanup and SetupFiles Extract in Wix
Think upgrading completely to 4.0 is no good idea as this is under heavy development and think not thought to use for production code.
To be clear:
ISSetupFilesExtract - This is used by InstallShield for following Use Case:
When a Custom Action needs to run an executable helper file which should not be installed: Then during Install Runtime ISSetupFilesExtract temporarily extracts this executable helper file (and if needed additional files), a CA can run that executable and afterwards before terminating the installation these temporary helper files get removed by the ISSetupFilesCleanup AFAIR.
This use case is in my eyes rarely used. A more frequent use case is to call an executable which is also installed and therefore such a temporary extraction is not needed
WiX Toolset Users Mailing List provided by FireGiant https://urldefense.proofpoint.com/v2/url?u=http-3A__www.firegiant.com_&d=DQICAg&c=ZgVRmm3mf2P1-XDAyDsu4A&r=yAhF6NGJ7EPmZkvswZOswwnYxaueKkO53V282tTn1P4&m=b86zpa4jBc2lttaPT9Ff7YCdgrxu3aw6P8w7qXf4Doo&s=4CTB94u-J8_rvmZoCH7kFqelbBJufkFT3dSCYvuhp5M&e=
More information about the wix-users