I use Wise Package Studio and within the MSI tool under the MSI Script Tab you can call either JScript's or VBScript's as Custom Actions. Is one preferred over the other? Is it better to only call VBScript's since your Windows OS should support them without any tweaking?

And I have read on many sites that one does not want to call JScript or VBScript Custom Actions if one can help it. That it is bad practice due to the fact that you don't know the state of the target machines and the fact that on Uninstall the Custom Actions are not Undone. What have most of you done in this area?

Thank you.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I used to use custom actions for file permission in a locked down environment. But I realized that using tools like group policy gives me more controlled and reliable results for those tasks. So now I try to stay away from custom actions as much as possible unless I am chaging the installation sequence or such.
Answered 04/02/2007 by: Deployment_Tech
Senior Yellow Belt

Please log in to comment
0
mhsl808,

The reason the custom actions are part of the install is in case there is a something that needs to be done before/during/after the install that the MSI does not/cannot due otherwise. I had an install one time where I had to replace an INI file in a vendor's MSI and the MST would not overwrite the file so I installed my INI in a temporary location locally then created a custom action vbscript that check for the target file and source file and copied the source over top of the target. This custom action was run right before InstallFinalize.

And, yes, I prefer vbscript over jscript because of native compatability.
Answered 04/02/2007 by: Cygonz
Senior Yellow Belt

Please log in to comment
0
I used vbscript extensively when I first started packaging, but I have since found I can do most things through the msi itself. I really only use a vbscript now to remove an old winstall package we have on the network or to fix issues with roaming profiles.
Answered 04/02/2007 by: spottedcoin
Senior Yellow Belt

Please log in to comment
0
Both are good as long as you know the client has vbscript or jscript support. In a corporate environment you will know if all clients has these core components or not.
I guess most want to use DLL CAs as you're not dependent on the support pre-installed on the client.
If you author a custom action to do something you will have to make sure to revert it during a rollback.
Answered 04/02/2007 by: AngelD
Red Belt

Please log in to comment
0
Yes, there's nothing wrong with using CA's (jscript or vbscript).. just be sure to code them correctly. With proper condition statements and sequencing, they are very effective with no drawbacks.

I use vbscript because most other companies do and it's a skill that's more portable to other environments... but jscript is fine too.
Answered 04/04/2007 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity