If I set an environmental varriable inside my installer feature#2 how do I refresh the environment in Windows XP so that Feature#3 can see the change and act on it?
That can be tricky; Windows supports that WM_SETTINGCHANGE message that native code can call, but not every process listens to it. Is it an option to use an ISMP property in parallel with the environment variable change?
RobertDickau wrote: That can be tricky; Windows supports that WM_SETTINGCHANGE message that native code can call, but not every process listens to it. Is it an option to use an ISMP property in parallel with the environment variable change?
That sounds like a good idea for future planinng but I can not use it in this case.
How would I use the WM_SETTINGCHANGE message inside my project? A assum this would be a custom action written in Java? Or an external exectable written in C?
