Yeah, removing the app's dependency on the environment variable would be the way to go. Unfortunately, that's not an option in this case. The weird thing is if you go look at the environment variables in the control panel and click OK, it does get propagated to subsequent command prompts. So there's something the installer is not doing. Also, I've only seen this in Windows 2003. It works as expected in Windows 2008.Thanks,JW
--- On Wed, 6/24/09, John Ludlow <john.ludlow...@gmail.com> wrote: From: John Ludlow <john.ludlow...@gmail.com> Subject: Re: [WiX-users] Environmet Variable Propagation To: "General discussion for Windows Installer XML toolset." <wix-users@lists.sourceforge.net> Date: Wednesday, June 24, 2009, 9:04 AM If I remember correctly, environment variables are only written on InstallFinalize. Once the installation completes, the environment variable should be available. I think I ran into this once before, and our answer was to change the application (a config utility we would run as part of the install) to not require an environment variable. I don't know if that is a good answer for you, but maybe it will offer some insight. HTH John 2009/6/24 Sascha Beaumont <sascha.beaum...@gmail.com>: > I've noticed that InstallShield sometimes uses it's own Custom Actions > for what you might think are fairly simple operations. The best bet > would be to create a basic MSI from InstallShield, decompile it, and > see what the resulting wxs looks like. > > On Sat, Jun 20, 2009 at 2:55 AM, JW<improvi...@yahoo.com> wrote: >> Some legacy components of our application require an environment variable >> that we are setting with the Environment element. This is the WiX code: >> <Environment Id="SetHome" Action="set" Name="APPHOME" >> Value="[INSTALLLOCATION]" System="yes" />. On Windows 2003 it is not >> propagated to Command Prompt windows that are opened in the same session. >> (This happens with both 3.0.4805 and 3.0.5271.) The variable shows up the >> control panel (and the registry), so it has been set properly. The kicker is >> that with the old InstallShield installer, the variable IS propagated to the >> child windows. Does anyone have any insights or suggestions? What is >> InstallShield doing that MSI isn't? We really don't want to have to prompt >> the user to reboot. I tried adding a custom action that broadcasts a >> WM_SETTINGCHANGE message, but I assume the installer does that already. >> >> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables unlimited >> royalty-free distribution of the report engine for externally facing >> server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> 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 > ------------------------------------------------------------------------------ _______________________________________________ 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
