Scripting Question

How to convert a vb script .vbs file to .msi using InstallShield 2010

07/08/2013 7001 views

I have created a vb script .vbs and it could run perfectly. I would like to convert the script created from .vbs file to .msi using installShield 2010. Could someone please kindly help me how to achieve this?

1 Comment   [ + ] Show comment


  • Depends on what your script does.
    If it's a simple file copy and some registry entries then you could use the Repackager to snapshot what your script does to produce an MSI

    There isn't a native method of converting vbscript to an MSI - you have to author your MSI to perform whatever actions the script does.

All Answers


my 50ct

worst case if you want to keep your vbs intact: 

Just add the VBS as a custom action in your MSI

This would not be my preferred way ..but if you only want to have a MSI  because that is the standard... please be my guest.

IF you use this method, please also create a rollback and  or Uninstall and / or  Repair VB.


(Which makes it more complex and therefore maybe easier to convert / translate your VB to the MSI in the first place)



Answered 07/09/2013 by: jaybee96
Red Belt

  • I copied the code and pasted to script in custom action to create .msi, it failed. Not sure what is wrong?
  • is custom action in a squence (what location) and is it Immediate or Deferred?
  • Haven't got the pc with the program to check at the moment.I think it is immediate. Do you think if it coud be the language in my script might not be recognised by the installshield?
    • This may help: http://www.itninja.com/blog/view/appdeploy-com-gt-training-videos-gt-custom-actions-with-installshield-adminstudio
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ