Stefano Tommesani

  • Increase font size
  • Default font size
  • Decrease font size
Home Programming Building Installshield LE 2012 setups from the command line for CI

Building Installshield LE 2012 setups from the command line for CI

In Visual Studio 2012, after installing Installshield LE 2012, you can include setup projects into your solution, as shown below:

AutoSetupSolution

Adding the Setup project to the solution, and including it into the Release configuration, makes for a quick, 1-click compilation procedure of both the main app and the installer. Still, what if we want to use a Continuous Integration software (e.g. Jenkins and countless others) and run the compilation of the setup from an external app? The ISL file extension used by InstallShield LE does not seem to be directly supported by CI softwares, and using ISCmdBld.exe as specified in Flexera's docs is not feasible, as that part of Installshield is missing from the LE edition (the L stands for Limited, so no surprises here). However, this specific project type can be compiled within VS IDE, so we can use MSBuild to compile it from the command line.

 

Let's start by defining a configuration for the solution that includes only the Setup project, using the SingleImage configuration:

 

AutoSetupConfigurationManager

When building the solution using this configuration, only the Setup project will be compiled.

Then let's open a command shell that supports the VS build environment (you can find in the Visual Studio Tools folder in the Start menu), and from the directory that contains the solution let's type the following command:

msbuild <name of solution.sln> /t:Rebuild /p:Configuration=SingleImage

AutoSetupCommandLine

In the ValidateProjects phase, MSBuild will report that all the other projects included into the solution are not enabled in the given configuration (SingleImage), then it will start compiling the InstallShield project. At the end of the process, after some warning messages highlighted in yellow that for now we are not considering, the output folder will contain the freshly built Setup file:

AutoSetupFinalFile

Quote this article on your site

To create link towards this article on your website,
copy and paste the text below in your page.




Preview :


Powered by QuoteThis © 2008
Last Updated on Thursday, 31 October 2013 12:45  
View Stefano Tommesani's profile on LinkedIn

Latest Articles

Unit-testing file I/O 26 November 2017, 12.09 Testing
Unit-testing file I/O
Two good news: file I/O is unit-testable, and it is surprisingly easy to do. Let's see how it works! A software no-one asked for First, we need a piece of software that deals with files and that has to be unit-tested. The
Fixing Git pull errors in SourceTree 10 April 2017, 01.44 Software
Fixing Git pull errors in SourceTree
If you encounter the following error when pulling a repository in SourceTree: VirtualAlloc pointer is null, Win32 error 487 it is due to to the Cygwin system failing to allocate a 5 MB large chunk of memory for its heap at
Castle on the hill of crappy audio quality 19 March 2017, 01.53 Audio
Castle on the hill of crappy audio quality
As the yearly dynamic range day is close (March 31st), let's have a look at one of the biggest audio massacres of the year, Ed Sheeran's "Castle on the hill". First time I heard the song, I thought my headphones just got
Necessary evil: testing private methods 29 January 2017, 21.41 Testing
Necessary evil: testing private methods
Some might say that testing private methods should be avoided because it means not testing the contract, that is the interface implemented by the class, but the internal implementation of the class itself. Still, not all
I am right and you are wrong 28 December 2016, 14.23 Web
I am right and you are wrong
Have you ever convinced anyone that disagreed with you about a deeply held belief? Better yet, have you changed your mind lately on an important topic after discussing with someone else that did not share your point of

Translate