Though we package applications using the following methods,

1. Setup Capture method to produce MSI file
2. TRANSFORM method  creation to produce MST file
3. Silent response methods to produce ISS file etc...

We still need an install script that will install the package in the commandline. We often use BATCH files and VBScript files. For VBScript install scripts my friend ESHWAR has written an excellent article:

Installation Wrapper [vbscript] with Reboot Timeout for Software Delivery

I'm going to use command files [Install.cmd/Uninstall.cmd] for my day-to-day packaging and deployment in windows7x64 environment. Following is the default template that I use in my current project and I hope this can be useful for most of you who have not implemented or about to implement standards around install scripts.

Requirements:

1. The application should be installed in near silent or silent mode
2. standard LOG file should be generated under C:\SWDLogs folder
3. Exit codes 0, 1641 & 3010 means success and everything else is failure 

Install.cmd

Exit %insterror% 

=======================================================================================

Uninstall.cmd

=======================================================================================

Some useful Naming Conventions:

Naming conventions plays a major role in standardizing the processes. We have the following naming conventions:

In case of Setup Capture MSI name should be as follows:

PKGID-Vendor-ApplicationName-Version-ReleaseVersion.MSI

In case of Transform creation method, MSI name should not be modified. However the TRANSFORM name should be as follows:

PKGID-Vendor-ApplicationName-Version-ReleaseVersion.MST

PKGID is a unique identifier for each package. Release Version starts from 1.0 and incremented when the package is reworked. This will ensure the tracking of how many times the package has been reworked.

I hope this information helps somebody. Thank you.