Well, it's certainly not a Wix issue, but environment with batch files can be affected. Check out SETLOCAL ENABLEDELAYEDEXPANSION (setlocal /?). Especially if the environment variables are used in loops, the standard dereferencing (%some_variable%) will not work properly. Enabling the above allows the use of delayed expansion with this syntax (!some_variable!). -- John M. Cooper Volt at Microsoft
-----Original Message----- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Friday, May 21, 2010 3:17 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Environment 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 that. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Environment-Variable-not-set-until-much-too-late-tp5076719p5086528.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
