I've seen a post or two about a situation wherein the environment Path is modified to include a new directory reference which is to be used later during the same installation session. Specifically, I have used the Environment element to append a directory reference to the Path variable then, later in the installation sequence, I have a Custom Action that runs regsvr32 to register in-process COM objects (i.e. DLLs). These DLLs have references to other DLLs elsewhere in the somewhat extensive target directory structure. The CA (regsvr32) fails due to its apparent inability to figure out the DLL's dependencies (i.e. other DLLs in other sub-directories that are being pointed at by the new directory references in the just-updated Path value.
Research seems to indicate that running processes (like the msiexec) don't "see" these updates as a routine matter but instead have to be "told to refresh" their copies of the environment values via some SendMessageXXX broadcast. My question is: how does one go about doing this? ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
