Custom Actions in WinInstall 8.7
It's been a while since I packaged so please bear with me. I used Wise to create packages in the past and creating custom actions was simple. I am trying to create a very simple custom action to run a vbscript to kill a process using pskill.exe. The script works if I run it manually but I can't seem to get the custom action to fire.
I create the custom action using the wizard and selected vbscipt and included the script in the package.
I set the custom action in the the Install>Execute Sequence and gave it various sequence numbers but I want this custom action to run before any files are copied. The msi log files does not even show the custom action running.
Please help with what is probably a very simple task that I'm just missing.
I create the custom action using the wizard and selected vbscipt and included the script in the package.
I set the custom action in the the Install>Execute Sequence and gave it various sequence numbers but I want this custom action to run before any files are copied. The msi log files does not even show the custom action running.
Please help with what is probably a very simple task that I'm just missing.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
JimA
15 years ago
I was able to take the same type of custom action and get it working using an eval version of Wise but I need to figure out how to get this working in WinInstall. Any suggestions would be greatly appreciated.
Posted by:
jmcfadyen
15 years ago
copy the CustomAction table row from your working Wise package into the WinInstall version.
Also it would be better to use an EXE custom action as using a VBScript and shelling out to other processes potentially can be problematic depending on security.
Once in vbs you can lose context of the calling user by shelling out to other processes. If you use an EXE CA it will be more likely to run in the desired context you intend to use.
Also it would be better to use an EXE custom action as using a VBScript and shelling out to other processes potentially can be problematic depending on security.
Once in vbs you can lose context of the calling user by shelling out to other processes. If you use an EXE CA it will be more likely to run in the desired context you intend to use.
Posted by:
JimA
15 years ago
Thanks I took your advise and change to use the exe. Can you tell me how to do this without importing the CustomAction table row from my Wise package? This would save me a bunch of time when I try and convert the rest of my WinInstall packages to MSI files. Also I only have a 30 day eval of Wise and I'm sure I wont be able to finish my conversions by then.
Thanks again for any help provided
Thanks again for any help provided
Posted by:
JimA
15 years ago
I looks like I had to put in the full path to the executable even though it said it was optional. Has this happened to anyone else? At least its working now.
Posted by:
jmcfadyen
15 years ago
it shouldnt need the full path,
can you post what your putting in your CA table
Action, Type, Source Target
i.e. Blah,1058, [blah], null
can you post what your putting in your CA table
Action, Type, Source Target
i.e. Blah,1058, [blah], null
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.