The deal is that I need some data to be saved between custom actions. One
custom action in some case could retrieve some Windows Firewall settings and
preserve them during an upgrade. The easiest and probably only way to do this
is by using some permanent store that can be read by a second custom action.
That store can be anything. Can anyone confirm that by design, MSI runs custom
actions in several DLL sessions, that is, for each custom action the Windows
Installer loads the DLL and unloads it upon completion? Otherwise this store
could be as easy as a global structure, and not as hard (not hard at all, just
another level of indirection) as a registry key.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
