[wix-users] How do I handle SetupFilesCleanup and SetupFiles Extract in Wix

[Shobha Dashottar]

Finally got this implemented.

I added the SupportFiles to the Binary Table. Wrote a custom action to query the Binary table and Extract the Binaries from the table . There are a lot of good examples out there for doing the extraction of the binary data and creating the binaries.

Thanks for all the responses .


-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Phill Hogland
Sent: Tuesday, September 06, 2016 7:44 PM
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

I have converted many InstallShield InstallScript setups to use WiX, and in all of these situations the files that used to be in the 'SupportDir' were addressed in two ways.

1) Those files for which the bootstrapper needed access too, where added as payloads, children of the BootstrapperApplicationRef element.  You can look at the wix source src\Setup\Bundle for examples of doing this.

2) Those files which were needed by a CA, were as others have already responded included in the Binary table.


For #1 I originally used a WixStdBA and shifted to using my mba, so there was not much if anything that I needed to carry over from the InstallShield setup.exe dependencies in the SupportDir that related to my new bootstrapper.  But if your concern is a bootstrapper issue then WiX already automatically supports the behavior that you are looking for.  Just use ProcessMon to look at what you wix bundle is doing to see this point.


For #2 there are many very good examples of using the WcaUtil to write clean property driven custom actions in C++ so I highly recommend that you study the source for the various WixExtensions, which in the end will also most certainly eliminate any need to emulate the SupportDir concept.  And if you prefer C# then there are many examples of achieving your goal using DTF.

________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Shobha Dashottar <Shobha_Dashottar at symantec.com>
Sent: Tuesday, September 6, 2016 1:17:06 AM
To: WiX Toolset Users Mailing List
Subject: Re: [wix-users] How do I handle SetupFilesCleanup and SetupFiles Extract in Wix

Yes. We do need the support files at the time of installation.  Depending upon the user's choice of feature we need to run some scripts/commands.  The ISSEtupFilesExtract was taking care of putting the support files in the temp folder. I see that now I need to write an custom action for this purpose . Going through the Windows Installer Function Reference I haven't hit anything yet .
I am exploring the MsiOpenPackage function but not sure that is the right direction.

Has anyone dealt with this before ?

Thanks
Shobha




-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Tobias S
Sent: Friday, September 02, 2016 7:10 PM
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

Lewis, you are right. If you have one executable you can use that as you described.

The support files construct is needed e.g. when you have an executable which depends on additional config or dll files for running it.

For me in some dozens of installers I used that Support Files once. But InstallShield adds the needed custom actions (ISSetupFilesExtract + ISSetupFilesCleanup + ...) always AFAIR...

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/