[wix-users] Handling files that are not part of initial install

[Patterson, Brent]

I read the 'WiX 3.6: A Developer's Guide to Windows Installer XML", and on page 397, it mentioned turning off package caching by setting the package's "Cache" attribute to "no" in the burn bundle.  I've tried this, but it still points "SourceDir" to the PackageCache in ProgramData.

The custom action is a deferred action that occurs after the installation is done.  I set the "DestFolder" and "SourceFolder" like this:

<CustomAction Id="SetFolders" Property="CopyConfigIni" Value="DestFolder=[INSTALL_DIR];SourceFolder=[SourceDir]" Execute="immediate" />

DestFolder points to the correct folder, but SourceDir points to the cached location, not the original msi folder.

Any ideas?  What can I do to make this work?

-----Original Message-----
From: wix-users [mailto:wix-users-bounces at lists.wixtoolset.org] On Behalf Of Patterson, Brent
Sent: Monday, August 31, 2015 2:13 PM
To: wix-users at lists.wixtoolset.org
Subject: [wix-users] Handling files that are not part of initial install

I ran into another issue with converting from InstallShield to WiX.  This one is about config files that can be modified by administrators for silent installs.  In Installshield, there's a custom action that copies those files over after the initial install is installed.  It references to "SourceDir".  I checked, the "Uninstall" registry records its location as the place where it was ran from.  When I try and replicate this in WiX, the "SourceDir" points to PackageCache location in ProgramData folder, causing this to fail.  This is for MSI, not burn bundles, but I do run the MSI from a burn bundle.

So there's two options, but I'm not sure how to accomplish either:

1.       Have the SourceDir point to the actual location of the installer, not the cached location that it was copied to.  This is the original behavior, and I'd like to replicate this if possible.  I tried setting Feature element's "InstallDefault" to either local or source, but it doesn't seem to do anything.  I think maybe this is a bit too late in the sequence of events to change anything.

2.       If the above isn't possible, somehow include the files that's not part of the MSI install as part of the caching process, so that it won't break the custom action.  I'd prefer to preserve the relative folder path.

How can I accomplish one of those?  I've scoured the internet trying to find answers, but I'm stumped.  Thanks.

________________________________

Xactware's opt-in mailing list allows you to receive Xactware News that is of interest to you. Visit my.xactware.com today to join or to update your email preferences!

________________________________

This email is intended solely for the recipient. It may contain privileged, proprietary or confidential information or material. If you are not the intended recipient, please delete this email and any attachments and notify the sender of the error.

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