CharlesAnthony
Posts: 18
Joined: Wed Oct 07, 2009 9:45 am

Custom Actions DetectProcess and StopProcess

Hi,

I'm writing an installer that needs to be run in /PASSIVE mode (i.e. no user intervention), for both installation and removal.

For the latter, removal, I understand I need to stop the installed application before InstallValidate, to prevent a reboot because of files in use. I've read
http://www.advancedinstaller.com/user-g ... ocess.html but it's not quite clear to me what should go in the ActionData field. Is it the full path to the .exe? Or is it the "name" of the .exe?

For example, if I have an exe APPDIR\bin\My Program.exe, should ActionData be

"[My_Program_exe_1]"(the Installation File, quoted, as provided by the Edit Custom Action Parameters)
[My_Program_exe_1] (the Installation File, not quoted)
"My Program" (The name of the .exe, no extension, quoted)
My Program (he name of the .exe, no extension, not quoted)
"My Program.exe" (The full name of the .exe, no path, quoted)
My Program.exe (The full name of the .exe, no path, not quoted)

Or should it be some other value that I haven't thought of yet?

And, as a follow up, I assume the same value should go into the ActionData of StopProcess, too?

Kind Regards,

Charles
CharlesAnthony
Posts: 18
Joined: Wed Oct 07, 2009 9:45 am

Re: Custom Actions DetectProcess and StopProcess

Working my way through the list, I have found that the answer to this appears to be

My Program.exe

i.e. the full name of the .exe, without the path. It doesn't need to be quoted.
Bogdan
Posts: 2794
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Custom Actions DetectProcess and StopProcess

Hi,

This is correct for both of the custom actions.

Please let us know if you have other questions.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”