Consider the scenario: RTM install is updated via QuickPatch to Update 1. Now I would like to create a regular, sequential patch via Patch Design that goes from Update1 (QuickPatch) to Update 2 (Patch Design). It doesn't seem possible unless maybe I do a full install rebuild of RTM that includes the updated files of Update1. UPDATE: I've tried rebuilding RTM to contain the modified files from the QuickPatch, and built Update 2 (Patch Design) off that. It doesn't work. If the user installs RTM, updates to Update1, then attempts to apply the Update 2 they still get an error. Is there a way to go from Quick Patch to Patch Design? In other words, it seems that once you create and use a QuickPatch you are committed to using QuickPatches throughout the rest of the product's life for updating. There doesn't seem to be a straightforward way to go from QuickPatch to Patch Design Patch. IE: In Patch Design, when you enter previous versions it is asking for an .msi file, there's no option to enter a QuickPatch file. ... View more

Using a 2016 Suite project file, I want to specify the location for my exe package. As it exists now they are put into a default location which is some random guid folder, ie: {8E1D8440-2F2E-46D2-B2C3-7E31BF5F7BC5}. But in my dvd, we do not put our exe in a folder named {8E1D8440-2F2E-46D2-B2C3-7E31BF5F7BC5}. I would have thought there would be an easy way to specify where the exe is located, and point the "Location" to that folder. But it doesn't appear to me there is such an option available. I would really prefer not to have to specify "Extract from setup.exe" since the packages are large and would balloon the size of the suite's .exe. And I'd be very surprised if i'm the only one who has ever run into this situation, but I am not seeing anything on the forums about what I would consider to be a very common and basic need. Is there a way to specify the location of the exe? Am I just blind and do not see it? Thanks! ... View more

When I look through my msi log files I see lines that begin with: MSI (s) (88:DC) MSI (c) (9C:80) Property(S): Property(C): What do the (s), (c), (S), (C) stand for? I have a hunch it refers to the sequence the setup is in at the time, UI sequence or Execute sequence. But I'm not 100% sure about that. Also, the (88:DC), (9C:80), (9C:E4), (88!18), and a few others....what do they refer to? ... View more

In my InstallScript project, I want to modify the SdFeatureTree dialog such that the description text control uses a vertical scroll. This is because I have large amounts of text to display for each feature's description. I go to "Other Windows Styles" and check WS_VSCROLL. When I run the project the vertical scroll bar appears, however, it is disabled. What else needs to be done in order to have the vertical scroll be enabled and work? ... View more

I'm using a test msi installer: I have two features: FEATURE_1, FEATURE_2, both have a file linked to them. However, with FEATURE_1, I also have a merge module linked to it. Now I run the install with the following command: msiexec /i Test_Installer.msi ADDLOCAL=FEATURE_2 /qb. The result is FEATURE_2 gets installed as expected, the file from FEATURE_1 does not get installed as expected, but the merge module from FEATURE_1 does get executed. Why is this? ... View more

It appears that, starting with Installshield 2015, signtool.exe is no longer installed with the standalone build product. Does anyone know why and if it will be back in some later release? Thanks. ... View more

I'm having difficulty getting the shareddll reference count for a file that is installed on my machine. In the registry the reference count for this particular file is 3. When I call this function it is always returning -1. Here's how I am calling it: NUMBER nCount, rnVal; STRING sCount, fileToCheck; begin fileToCheck = CommonFiles64Folder ^ "MyCompany\\myfile.dll"; rnVal = GetFileInfo (fileToCheck, FILE_SHARED_COUNT, nCount, sCount); What am I doing wrong? ... View more

This post is pertaining the QuickPatch project file. I wasted hours on an issue as a result of a very inaccurate description for a check box in the QuickPatch project file. In the QuickPatch IDE, "Files" view, on the right is the "Updated File" section. Just below the text field is a checkbox with a pretty good and lengthy description about what it does: "Overwrite Any Existing File - Select this option to include this file into your setup as a whole file. This will allow you to patch over any previous version of the file. Non-versioned files will always overwrite when this option is selected." I read this description and thought, "this is exactly what I need!" In my situation, the file I need to update has a version of 17.0.0.0, and the latest file has the same version. I thought it was a slam dunk. But the file would not update. I spent so much time trying different things and doing google searches. Finally I stumbled upon the documentation for this checkbox http://helpnet.installshield.com/installshield18helplib/QPAppFileModifiedCommonTab.htm. It says that when this option is selected, Windows Installer considers the selected file to have a version of 1.0.0.0, and the file with the highest version wins. This is ONLY useful if both the target and selected file are unversioned. This check box description is very misleading and inaccurate, and hopefully someone from Installshield will change it to save some other user a lot of time and frustration. ... View more