Software Deployment

An MSI does not contain an MST inside. An MST is created with your changes and applied to the MSI, at installation, to modify how the installation is performed. If you want to change how/what an MSI installs, you would have two options: 1) Modify the MSI directly (not a good idea with vendor MSIs) or 2) create an MST with the changes based on the original MSI and apply the MST at installation (including additional files). Once an MST has been created the installation command would look like this: msiexec /i "your.msi" TRANSFORMS="your.mst". To understand further, buy you a copy of Phil Wilson's Definitive Guide to Windows Installer.

An MSI does not contain an MST insideIt can do. Google "embedded transform" :-)

@OP, if you're RE-packaging, you don't need a transform, since you would just add the additional DLLs (or whatever) before you complete the capture process. However, you say that the package is already an MSI, in which case you will probably want to use InstallShield's 'Tuner' to create your transform. Once you have the MST, open it in AS and just add the files. Remember that MSTs cannot contain files so you will need to have them added to an external CAB.

It also sounds like you want to have a one-piece package so use AS's facility to create an EXE-type installer. This will incorporate the MSI, MST and CAB which will get extracted and executed at install-time.

Please throw some more light on the processes

Uggghhh...

Sorry, I don't have the time to give you a step-by-step guide. I doubt many others here would, either. Search AppDeploy for "definitive guide" and take it from there.