Software Deployment

This is pretty straight-forward in Installshield. Open the Editor, create a new "Basic MSI project". Make whatever changes. Save as, change the file type to "IST".
To use your template when repackaging. Do your snapshots. When you open your IRP in the Repackager Editor, there's a option to browse to an IST template on the "Repackaged Output" node. It will apply these changes when you build your ISM.

talking about using vb scripts to customize the packaging process

That's a massive subject there's loads you can do.

We use WPS workbench and have created 2 processes one for capturing an app and the other for creating a transform for a vendor app.

The steps look very roughly like this:

-Documentation - Vbscript to launch word and populate a standard template obviously specific detail for app is added by packager
-Setup Environment - vbscript to create folder structure pertinent to our environment
-Capture package - use wise task to run setup capture
(for transforms use vb script to copy vendor msi then edit this and use a wise task to run msitran)
-Backup files - vbscript does this (there are backups all the way through the process)
-Edit package in orca or wise - use wise task to run tools
-Apply our standard corporate settings - vbscript to add settings
-Citrix customisation - vbscript to apply standard changes
-Conflict management - use wise task to run tool
-QA - use wise task to run test expert
-Distribution - vbscript to create sms package/collection/advert

ORIGINAL: bob_msi
talking about using vb scripts to customize the packaging process


Could you possibly be any more vague or lazy in your posting?