I thought MSI did the send message thing itself and that console windows are never affected by it.
On Mon, Dec 17, 2012 at 4:31 PM, Mita Patel <mpa...@esri.com> wrote: > We are having issues propagating the environment variables. The setup has > a custom action that propagates the environment using the > SendMessageTimeOut api > > SendMessageTimeout(HWND_BROADCAST, WM_SETTINGCHANGE, 0,(LPARAM) > "Environment", SMTO_ABORTIFHUNG, 5000, NULL); > > On a 64 bit OS, both 32 and 64 bit consoles were opened before the > install. Ran the install with the above custom action. If a console window > is open one doesn't see the custom Environment. But open a new console > session and the varaible is listed (for both 32 and 64 bit cosole). Is > this the correct behavior? Is there a way for the console window opened > before the install to see the custom environment variable. > > Thanks > Mita > > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching http://RobMensching.com LLC ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
