About adboll

adboll · ‎Sep 22, 2014

Repair worked for this. I just hope the repair did not regress the Flexera plugins I had installed for 2014. Thanks all! Flexera should allow you to set this somehow via Windows native file association functionality or a proprietary solution. Running a repair on whatever version you want to default open an .ism project is not really a desired solution.

adboll · ‎Jul 31, 2014

I am familiar with how Windows file associations can be set/are set, but for the life of me, I cannot seem to find a good way to get projects built in Installshield 2014 to open in Installshield 2014 when you double click them. I have to run Installshield 2014 and open the projects from there. 2013 seems to be the default. I keep 2012, 2013, and 2014 on my machine for backwards compatibility reasons. I have multiple attempts at the registry and file associations. Anyone have an idea?

adboll · ‎Apr 29, 2014

For the operating system conditions, I went by Microsoft's download page documentation of: "Microsoft .NET Framework 4.5.1 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows Server 2008 SP2 Windows Server 2008 R2 SP1 and Windows Server 2012" The reg key using the version number I found on my own, but I guess any of the three will work. You may not want to include the condition for release 378675 because I looked it up and that is the Release Candidate. It will work, but if you only want the latest, only include the release 378758.

adboll · ‎Apr 02, 2014

MichaelU wrote: You've enumerated your options fairly well. The primary questions I would use to answer this are as follows: How much is shared between the three different options? Are the release cycle of all three tied together? Is there a lot of complexity in any part or in aggregate? If there is a lot of complexity, or if the release cycles may be separate, I would err towards separating it into smaller basic MSI projects. If it's more than one package per selection ("server" and "client" might both rely on a "dependencies" package), I would make a Suite project to install these MSI packages. If it's not particularly complex, and the release cycle is shared, I would err towards making this features and components in a single basic MSI project, and optionally deliver it with a Suite project. In either case you can create a wizard experience that allows a user to select only a single option (powered under the hood with features), or one that allows selecting any combination by using the normal feature selection UI. What is the best way to do this "mutually exclusive"? MichaelU wrote: In either case you can create a wizard experience that allows a user to select only a single option (powered under the hood with features),

adboll · ‎Jan 24, 2014

I created a prerequisite to call the PostgreSQL installer by command line with switches. Hopefully this works. Is there a better way to install it? Once PostgreSQL is installed, I need to run a SQL script to create the database and tables. What is the best method for doing this since it appears InstallShield supports several SQL RDBMSs except PostgreSQL?

adboll · ‎Jan 24, 2014

I am a fairly new user to InstallShield products. I have built several basic MSI and MSP projects and am slowly learning this software. I currently have an application that needs 3 different installation options in regards to architecture, not necessarily features. For instance, I would like a dialog that allows the end user to select if they wish to install "Server", "Client", or "Training" for the same application. Each of these three platforms, if you will, contain products that are identical (no config differences), similar (same files but config is different), and unique (whole item exists in one platform but not the others). The problem I am having is what is the best project type to use to tackle this project??? Ideas I am tossing around are: Advanced UI/Suite (calling different MSI packages in features) with a custom dialog, Basic MSI (with several features and/or chained MSI packages) with a custom dialog, InstallScript (really don't know this that well). Or was InstallShield designed to keep this high level architecture separate all together (a disk for each platform)?

Online Status	Offline
Date Last Visited	‎Jun 19, 2019 10:43 PM

Re: Installshield 2013 opens for 2014 .ism projects, etc.

Installshield 2013 opens for 2014 .ism projects, etc.

My conditions and operating system conditions

How do I allow user to select mutually exclusive installs?

PostgreSQL installation and script

Installation Architecture