When you want to release a new version of your software, you often want it to replace the existing version. In order to do this in Installshield Limited setup projects, you need to understand the following items.
There are two different codes: Product Code and Upgrade Code.
Continue reading Installshield Limited: version bumping
Microsoft decided to drop the ability to create simple setup installers in 2012 but they worked with Flexera to allow us to use Installshield Limited to create our installers.
Below are the step required to create a simple installer. It should give you an idea how to create an installer for your VS 2012 program.
- First, you need to make sure that all DevExpress libraries (and other custom references) in your program are set to CopyLocal — this will have the build system copy the libraries to binDebug (or binRelease) so you can include them in the InstallShield project. Also be sure to build your app before creating the installer.
- Second, I’ve been creating entirely new solutions for each installer in a separate directory. This eliminates the problems 2012 has with opening the old installer types (and may prevent future problems with bundling). It also makes the build process much faster on the program you are creating.
Creating a new installer:
- Create a new InstallShield Limited Edition project for the installer (in ProjectsVB.NetInstallers)
- Application Information
- Set the default installation location if you don’t want the program to be installed in Program Files
- In the Application Information sidebar, click Edit the default installation location
- Right-click Destination Computer (or press INS key) and choose New Directory; name it C:
- Right-click the new C: directory (or press INS key) and choose New Directory; name it YourSubFolder (obviously change it and repeat as necessary to create your desired directory structure)
- Right-click new YourSubFolder directory (or press INS key) and choose New Directory; use the name of your project
- Specify company name: YourCompanyName
- Specify application name: YourAppName
- Specify application version: YourAppVersion
- Specify company website: YourWebsite
- Change the icon to your project’s icon (if desired)
- Installation Requirements
- App does not require specific operating system
- App requires .Net 4.0 Client Profile (but I do not include it in the installer — see Problems below).
- Application Files
- Click on the C:YourSubFolderYourAppName folder.
- Press Add Files button and go to your App’s bin/Debug (or bin/Release) folder and add all exe/dll/config files.
- Application Shortcuts
- Modify the name of the Start Menu shortcut (if desired)
- Application Registry
- Add registry keys if your App requires them. Use the INS key to add new keys and values (or right-click)
- Installation Interview
- Do not display License Agreement
- Do not prompt for Company/User name
- Allow modification of installation location
- Do not launch application when the install completes
- Organize Your Setup, General Information
- Set Use Software Identification Tag to No.
- Prepare for Release, Release
- Click on “Express” and set Setup File Name to YourAppName Setup
- Right-click on the Solution and choose Properties
- In Configuration Properties/Configuration, set your project to SingleImage.
- Build the project
- Verify the project installer name
- In Prepare for Release, Release, Builds/Express/SingleImage/Disk Image(s)/DISK1: check file name
I have not yet been able to include the .Net packages in the installer. The downloads from within the Installshield project always fails. Update: you have to run Visual Studio as Administrator (right-click, “Run as Administrator”) in order for the installer packages to download. This should be a one-time thing; just run as admin once to download all of the redist files you need and then open your project normally (without admin) to work on your project.
- I had to disable Use Software Identification Tag or it would give me an error upon building. The installer creates correctly without it and will install the project with no problems. When I get some more time I’ll look into this further.