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

Rob Mensching rob at firegiant.com
Fri Apr 12 09:23:36 PDT 2019

1. It has to be added to the engine (stub) since that is the process starting the ExePackage processes. Fortunately, there is already a message loop in the engine for handling shutdown messages.

2. It might be nice to add to the native BA but I'm not sure how useful that would be in practice since the native BA wouldn't be able to do anything with it.

3. Managed BA doesn't own the message loop so it isn't "in the loop" (ha, ha) to handle WM_SETTINGSCHANGED.

To get started, add an "EnvRefresh()" function (or better name) to a new envutil.cpp in https://github.com/wixtoolset/dutil. I expect that will be the hardest part. Then add the WM_SETTINGSCHANGED switch case to the message handling in the stub and call the new function.

That _should_ do it.


  Rob Mensching
 FireGiant  |  Dedicated support for the WiX toolset  |  http://www.firegiant.com/

-----Original Message-----
From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean Farrow via wix-devs
Sent: Friday, April 12, 2019 5:16 AM
To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
Cc: Sean Farrow <sean.farrow at seanfarrow.co.uk>
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