Hi All,

we planned to prepare automated build in install shield.We are maintaining the source code  in TFS.

1. How to do the automated build in install shield..? 
2. Is there any tool to automate the build process
3. If it is there what are the tools are there..? which one is best..?

Please share some ideas about it

Thanks for advance.

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer Chosen by the Author


In the past I have used.. ISCmdBld. If you have intallshield look at the help files or docs on that to figure out the full command you will need.
Answered 03/08/2016 by: Badger
Red Belt

  • ya i could trigger the build programmatically using iscmdbld.exe.My problem is adding files ..? i dont have experience in that
    • Adding files?? your iscmdbld.exe uses the project you create, an ISM. If you want to add a file, you have to add a component, put the file in that, save the ISM, then run the iscmdbld. You normally use the iscmdbld to schedule the MSI build at a time after developers create new code or binaries. If anyone wants to add a new file, not just an updated one, then you have to edit the ISM before running the iscmdbld.
      • Yes, we can add the files manually. we want to do it pro grammatically.
      • your best bet for programmatically, it would be LOT easier to do it as I said above.. but if you make sure your ISM is in XML format, you could programmatically manipulate the project file using XML. BUT, you are then in the same neck of the woods as WIX. so, tough place for you to be. good luck
Please log in to comment

Community Chosen Answer


Have you thought about using Wix? Most shops that I know who do automated builds use that.
Answered 03/08/2016 by: VBScab
Red Belt

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


you have two options,
1. command line
2. Use the COM interfaces from InstallShield with you preferred script language (vbs, powershell whatever...)

Dependent on what exactly you want to do (automation wise) the command line is quick & dirty if it's just compiling an existing ism. However if you want to do things like change the ProductCode / ProductVersion, perhaps with multi-language setups etc. then the COM interfaces are the way to go. This has a steeper learning curve, but allows more flexibility.

Answered 03/08/2016 by: Pressanykey
Red Belt

Please log in to comment