[wix-devs] Burn support for WM_SETTINGSCHANGED to refresh environment variables

Christopher Painter chrpai at iswix.com
Fri Apr 12 05:24:59 PDT 2019

FWIW, I wrote a (very functional) Frankenstein bootstrapper about 13 years ago using MSI.  It could never be silent but it could be /QR.   We used the MSI for the UI, feature selection, package content caching and other various things MSI can do  and then when we returned to the UI sequence where we used custom actions to start new processes to install the various packages.   This was to avoid the msi mutex constraints.

What does this have to do with Environment?  Well we understood that environment changes made by WriteEnvironmentStrings of some of the packages wouldn't be seen by MSI when installing the next package.  So we'd load the environment into the new process we were starting.

In other words.... should/could this be pushed back to the requester  as their bootstrapper application should handle this?

From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> on behalf of Sean Farrow via wix-devs <wix-devs at lists.wixtoolset.org>
Sent: Friday, April 12, 2019 7:15 AM
To: WiX Toolset Developer Mailing List
Cc: Sean Farrow
Subject: [wix-devs] Burn support for WM_SETTINGSCHANGED to refresh environment variables


Just following up to start the design discussion for this feature as requested.
Do we want to add this to both the managed and unmanaged bootstrappers?
Or, can we get away with just adding it to the stub?
WiX Toolset Developer Mailing List provided by FireGiant http://www.firegiant.com/

More information about the wix-devs mailing list