InstallShield 2020 R3 Version 26 I don't know the exact steps to duplicate this, and I don't know if this is the correct place to post this. I've also found a workaround. I opened an existing ISM file, and I think this file was created before I upgraded to R3 (not sure what I was on prior to this). Anyway, made a couple of changes (such as version number) and went to compile a new Setup.exe but it kept failing with an error about a Move File command. While trying to figure out why this was happening even though I hadn't altered anything to do with the Move File table in the MSI, I noticed it kept semi-launching the MSI near the end of the build process, which it hasn't done before and I found odd. I can't remember what I noticed in the build log after that, but it lead me to the Releases tab, where in my SINGLE_EXE_IMAGE I noticed that 'Build Windows App Package' on the APPX/MSIX set to Yes. I set it to 'No', and re-ran the build the process. The build process failed yet again for the same reason, and then the I noticed 'Build Windows App Package' was still set to 'Yes'. I set it once again to 'No' thinking maybe I miss-clicked, and verified that it was indeed set to 'No', and then re-ran the build. Failed again, and this time I watched as it reset itself back to 'Yes'. So basically I can't turn off APPX (which I don't need currently) and then build Setup.exe. ---------- As to my workaround: I set APPX to 'No' once more, I saved the ISM file, I closed InstallShield, I reopened InstallShield from the ISM file (double clicked the ISM file), I went to the Releases tab and verified that APPX was still set to 'No'. I ran the build once more. This time the build succeeded, and APPX stayed turned off. So to reiterate: it seems that if APPX is ON for whatever reason, you can't seem to turn off and build. You can turn OFF, close out of InstallShield and reopen and it will now be off. ... View more

I was trying to follow the guide found at: http://www.installationdeveloper.com/3251/installing-fonts-during-an-installshield-installation/ I go through the Component Wizard and select the font I want. Nowhere/at no time in the Component wizard is there the option to manually specify the component name. Instead it automatically generates the component name. No matter what I try, when I click finish I get the following error message: Component: An invalid identifier was supplied. The field may contain letters, digits, underscores (_), or periods (.). Then field must begin with a letter or an underscore. ^ The component name that is being generated has a dash (-) in it. ... View more

In Install Shield 2014, in the Upgrades View, the 'Add Automatic Upgrade Item' was the default and had a keybind of the Insert (INS) key. The 2014 manual also mentions that it is the preferred method (http://helpnet.flexerasoftware.com/installshield21helplib/helplibrary/Upgrades.htm) I recently upgraded to 2015, and it is no longer the default. 'Add Major Upgrade Item' is the default now (and is now bound to the Insert key). The manual (http://helpnet.flexerasoftware.com/installshield22helplib/helplibrary/Upgrades.htm#ref-views_3665898677_1024145) also no longer lists the Automatic as the preferred (albeit it doesn't list any of them as preferred). I actually preferred the automatic - it was one less thing for me to figure out and worry about. So my first question: is there a reason I should no longer be using the automatic option? My second question: is there a way to change the keybind back to Automatic so when I hit the Insert key (which I got into the habit of) adds that instead? And if so, how? (I tried poking through the customization options in the Tools menu, but didn't find a way) ... View more

I'm fairly new to InstallShield. One annoyance I have with building a new setup.exe, is that all the contents in the PROJECT_ASSISTANT\SINGLE_EXE_IMAGE\DiskImages\DISK1 folder are deleted on every build. I used to use a different installer product (the company is out of business). Anyway, in the other program I would build a new setup.exe, and then I would immediately rename that setup.exe to incorporate the version number - IE, if the version 1.0.0.0, then it would be named setup.1.0.0.0.exe When I build a new setup.exe with InstallShield (Spring 2012), the renamed setup.1.0.0.0.exe goes poof. I am now in the habit of just copying the setup.exe to a new folder and renaming it there. I was just wondering if there is a way to get it to preserve the contents of the DISK1 folder. If not, that is fine. I'm just trying to save on the extra step of copying the setup.exe elsewhere. (P.S. I tried googling & searching this forum every which way I could think of before asking this question). ... View more