What is currently displayed by your message box currently? I assume that you are able to at least display something hard-coded such as "Hello world" successfully? I think you should be able to pass [INSTALLDIR] on the command line to your vbscript script that you are installing with your product. ... View more

I am not sure why the custom action is not waiting for your command to finish executing. You may need to tweak your batch file so that it only finishes execution when all commands in it are finished. Try to put in a Pause statement in the batch file to see if the custom action at least waits for the duration of the Pause statement as a test. ... View more

Please see the following documentation: Creating a File Extension Association http://helpnet.flexerasoftware.com/robo/projects/isxhelp16/IHelpISXFileExtensionCreate.htm Does that help you to accomplish what you are looking to do? ... View more

Simply adding an install.cmd file as an application file will not cause it to be executed during the installation. It will just be treated as a file that needs to be installed. You should look into using a custom action to run the CMD file (perhaps with an EXE - Path referencing a directory custom action). Ideally you should only use such a custom action if the built-in Windows Installer functionality will not be sufficient to accomplish the same thing. ... View more

The multi-instance dialog is actually displayed by Setup.exe (bootstrapper) before beginning the actual MSI installation. Because of this it is not possible to hit Back button on the MSI dialogs to go back to the multi-instance dialog. It was necessary for this dialog to be displayed before beginning the MSI installation. This dialog location is similar to the setup.exe initialization dialog. ... View more

Hi, I think you have posted in the wrong forum. This one is for Basic MSI/InstallScript installations created with IS 2008... (not for multiplatform installs created with 11.5) -Ajay ... View more

You will probably want to look into configuring the new installations built with InstallShield as major upgrades for the installations previously built by the Visual Studio Setup and Deployment project. This way the new installs will seamlessly uninstall the previous versions if they are detected during the new install. Please look into the help library for more information about upgrading. Major Upgrades http://helpnet.flexerasoftware.com/robo/projects/installshield16helplib/MajorUpgrade.htm ... View more

Windows Installer does not have native support for Internet shortcuts, and for this reason, there isn't a good way of creating one in the InstallShield Shortcuts view. Instead you should consider either including the Internet Shortcut URL file as a raw file or using the Ini File Changes view to create an Internet Shortcut. Here is a KB article that should be helpful: Q105380: INFO: Creating an Internet Shortcut http://kb.flexerasoftware.com/selfservice/viewContent.do?externalID=Q105380 ... View more

You could try java.exe -version 2> example.txt This should redirect stderr I believe, and it worked for me with getting the version output from java.exe. ... View more

Hi, The response file for an InstallScript MSI installation allows you to specify default values for all of the IS MSI dialogs seen to facilitate a silent install. But since Setup Prerequisites are handled by Setup.exe before launching the IS MSI installation, the response file does not apply to Setup Prerequisites. During a silent installation, setup prerequisites will be installed if the condition of the prerequisite indicates that it needs to be installed. This is also the normal behavior when the install is run with full UI. I don't believe there is any command line switch to force setup prerequisites to install or not install during a silent install. -Ajay ... View more

Here are the steps I was able to use to debug InstallScript custom actions that are marked as "Deferred Execution in System Context": 1. I created a new basic msi project in IS 2010. 2. I added an empty feature and component. 3. I added a new default InstallScript file. 4. Added a MessageBox call in default MyFunction function. 5. Made a copy of MyFunction function to be called from a deferred execution CA. 6. Added two InstallScript custom actions. One is immediate and runs MyFunction, and the other is Deferred Execution in System Context and sequenced after InstallInitialize and runs the second function. 7. I built with default release options. 8. I added the following registry information to my IS 2010 system: HKEY_CURRENT_USER\Software\InstallShield\ISEngine16.0 DebugISCustomActions DWORD 00000001 9. I opened a CMD prompt window and went to the Disk1 folder of the setup. Then I ran the setup with /v"ISSCRIPTDEBUG=1". 10. The script debugger opened up on the immediate CA function call. I then set a breakpoint in the other function. 11. The breakpoint in the other function (from deferred CA) was hit next. Please confirm if the above steps work for you as well. If you move your setup to a different directory, then you probably need to also copy the Setup.dbg file found in the Script Files folder. -Ajay ... View more

Prerequisites included with previously installed versions of a product are not uninstalled during a major upgrade. Only the previous MSI is uninstalled. It is possible, however, that a newer version of a prerequisite that is included with your latest MSI may perform a major upgrade of its earlier version. ... View more

Hi Aaron, I think you are on the wrong track. You don't want to touch the Windows Installer registry keys you mentioned such as: //HKEY_CLASSES_ROOT\Installer\Products\(someguid) These are undocumented backend MSI inventory storage registry keys and should not be directly modified. Also, there is no need to modify them to create a successful upgrade. If you correctly configure a major upgrade, then your new install will uninstall any older versions and thus remove ARP entries associated with them. Correctly authoring a major upgrade includes changing the ProductCode, increasing the major or minor part of the ProductVersion, and creating a major upgrade item in InstallShield Upgrades view which automatically populates an Upgrade Table entry. Hope this helps, Ajay ... View more

It sounds like you have merge in the registry keys discussed in the following KB article: Q112187: BUG: InstallScript Debugger Does Not Debug Deferred, Commit, or Rollback InstallScript Custom Actions http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q112187&sliceId= Is this correct? Could you test in a brand-new sample project to see if you are able to debug a Deferred execution custom action? ... View more