Re: [WiX-users] Environment Variable not set until much too late

2010-05-24 Thread David Watson
, newValue); Dave -Original Message- From: John Cooper (Volt) [mailto:a-jc...@microsoft.com] Sent: 21 May 2010 23:44 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Environment Variable not set until much too late Well, it's certainly not a Wix issue

Re: [WiX-users] Environment Variable not set until much too late

2010-05-21 Thread Nick Ramirez
Is it possible that the child process (the batch file) is picking up the same environment as the MSI (parent process?) and in order for it to pick up the new environment variable it would have to somehow refresh its environment? I'm not sure how to do that. -- View this message in context:

Re: [WiX-users] Environment Variable not set until much too late

2010-05-21 Thread John Cooper (Volt)
Variable not set until much too late Is it possible that the child process (the batch file) is picking up the same environment as the MSI (parent process?) and in order for it to pick up the new environment variable it would have to somehow refresh its environment? I'm not sure how to do

[WiX-users] Environment Variable not set until much too late

2010-05-19 Thread glenneroo
I have a CA running after InstallFinalize inside InstallExecuteSequence sequence and it relies on an environment variable (HOME), however, the variable isn't being set until AFTER I completely finish the installation. Here's a snippet from my install log: MSI (s) (1C:24) [21:56:25:369]: