Hi.
I think that Advanced Installer lacks a Custom Action that allow creating a Mutex.
This would be very useful e.g.: Close applications that do not respond to (or that discard) a WM_CLOSE message.
Useful also to trigger application actions during install time.

How is that?

Hello and welcome to our forums,

I'm not sure I fully understand your request. Can you please give us more details about this? What kind of support would you like to see implemented in our custom action support?

All the best,
Daniel

Thanks for replying.

I'll make an example.
Our application has a tray monitor running under user "Manager". The upgrade is triggered and started by a Windows service running under a Administrator privileged users "Installer".
While upgrading, we need to comunicate to the tray monitor some actions, like "Close it self" or "Restart". Now this monitor waits for a Mutex signal (eg. GLOBAL\RESTART_MONITOR) to perform the action.
Maybe I'm mistaken, but I did not found in AI a way to start a process on an other user.

Mutex in AI could be used for interprocess comunication. A good example is to signal start/stop/progress of the install process to monitors, loggers or diagnostic tools.

PS: Our installer must be an unattendad, sincronized, multi PC upgrade system.

Regards
Ricardo

Hello Ricardo,

Thank you for your further feedback. I've forwarded it to our development team and for the moment such an improvement will have a very low priority for our product. If there will be other requests in the future maybe we will increase its priority.

In the meantime the solution for your will be to write from scratch your own custom action to create the desired mutex. For instance you can write your custom action as a .Net one.

If there is anything else we can assist you with just let us know.

All the best,
Daniel

Thank you for your replay
I'll insert the sugested solution.

Ricardo

You are always welcome Ricardo.

All the best,
Daniel