I have two MSMs with the same Module ID. One includes x64 files and the other includes x86 files. I would like to include them both into a single Basic MSI installer and set a condition so that one or the other is installed based on the target system. The problem is that I can't seem to get both MSMs to appear in the Redistributables view. I can fiddle with the search directory order in Tools -> Options -> Merge Modules, and I can manually specify one or the other by right-clicking in the Redistributables view and navigating to it, but doing so invariably removes the other. I can't get them to appear at the same time. Is this due to them having the same Module ID? They do have different file names and live in different source directories, and since they have different contents would have different MD5 signatures. Changing the Module ID of just one of the MSMs would be difficult considering how they are built (a single WiX script which substitutes contents based on platform) and also that those are "owned" by another group. It would be ideal if I could simply include both MSMs in my Basic MSI project as they exist now. Thanks in advance. ... View more

I have a Basic MSI installer that was targeted to x86 platforms (with a companion installer targeted to x64). We have removed the 64-bit components and would like to have a single installer that works on both platforms. However, the x86 installer refuses to run on x64 platforms. The Platforms value on the x86 installer reads "Intel;1033" which according to what I've read should work for both. The Platforms value in the Release view is blank. Where else can I look to remove the platform specificity and allow the single installer to work on x86 and x64? ... View more

When doing a fresh install of our product on XP, the "Computing space requirements" dialog is shown for an extended period of time and then an "Out of Disk Space" dialog is shown. Note that there is plenty of space, even as shown on the dialog itself. When installing the same product on Win7, again the "Computing space requirements" is shown for much longer than it should and then a "Could not access network location" error is shown. This is a self-contained downloadable .exe installer so there are no network locations that should be necessary. Please see the attached screen shots. I will happily provide any logging or other data but I'll need to know how to generate them. ... View more

I have an InstallScript Custom Action in a Basic MSI setup. I know the CA is called when setup.exe is run (it's a very simple CA that just shows a MessageBox). I am attempting to debug the CA on a remote machine. I have copied ISDbg.exe and SciLexer.dll to the remote machine, which is running Windows 7-64. I ran ISDbg /regserver. I verified that the InstallScript Debugger was correctly registered by remotely debugging a pure InstallScript setup. When I try to debug the InstallScript CA in my Basic MSI setup, the InstallScript debugger never launches. The CA runs and then the setup continues. I suspect the problem lies in the command-line I am passing to setup.exe. Information from the InstallShield help ("Setup.exe and Update.exe Command-Line Parameters" topic) suggests there are two ways to debug InstallScript CAs: /v"ISSCRIPTCMDLINE=\" \"" : pass arguments that should be passed to the script Basic MSI projects that have InstallScript custom actions This option specifies command-line parameters to be passed to the script. Any property supported by InstallScript MSI (where appropriate) can be specified. (The most common ones are /d and /z.) For example, the following indicates that you want to debug the script, and that the CMDLINE variable should contain TEST. Setup.exe /v"ISSCRIPTCMDLINE=\"-d -zTEST\"" Note that as shown above, when you want to specify that a double quote character is not a delimiter for the command line but a delimiter for the property, use \". Note also that as with any public Windows Installer property, this property should be specified with all uppercase letters. I tried: "\\vmware-host\Shared Folders\Downloads\setup.exe" /v"ISSCRIPTCMDLINE=\"-d\\WEBOS-IS-DEV\ISProjects\PreReqs\Script Files\"" /d : debug InstallScript Basic MSI projects with InstallScript custom actions, InstallScript, InstallScript MSI For an InstallScript project, running the command Setup.exe /d runs the installation program with the InstallScript Debugger. Debugging InstallScript code requires the debug-information file Setup.dbg to be available. To debug an InstallScript project on a system other than the development system: Copy the InstallScript Debugger executable file ISDbg.exe (located in the System folder of your InstallShield distribution) to the test system, and register it by launching the executable with the /REGSERVER command-line option. Copy Setup.dbg to the test system. Run Setup.exe with the command Setup.exe /d" ", where path is the directory containing Setup.dbg. For a Basic MSI project, the following command runs your InstallScript custom actions in the InstallScript Debugger: Setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"path-to-Setup.dbg\"" I copied the entire project folder to the remote machine and, from the DISK1 directory where setup.exe was built, tried: setup.exe /v"ISSCRIPTDEBUG=1 ISSCRIPTDEBUGPATH=\"C:\Users\Andrew Rich\Downloads\PreReqs\Script Files\"" In both cases, setup.exe launched and the InstallScript CA executed but the debugger never fired. What is the really correct way to debug InstallScript CAs in a Basic MSI setup? ... View more

Basic MSI project in InstallShield 2011. There's a need to set some user environment variables. Under System Configuration -> Environment Variables, I configured the name and value. The value needs to be a subdirectory named "SDK" under the installed directory so I set it to "[INSTALLDIR]SDK". This works fine as long as the user doesn't change the default install directory. If they do, the environment variable is still set to the default instead of the custom. I tried using an InstallScript custom action, setting the environment variable into the "Environment" key of HKEY_CURRENT_USER. The values are set (let's hear it for InstallScript) but again, it always uses the default value of INSTALLDIR even if I choose a custom install directory. What is the proper way to specify the true value of INSTALLDIR whether customized or default? By the way, Hi everyone. I'm back. Again. ... View more