You should be able to use CommonAppDataFolder location to get files to install to C:\ProgramData folder in Vista and newer. You may want to look into using the MoveFile table to copy an existing version of your applications Access database files to the new location. Otherwise you would probably need to create some kind of custom action to handle the requirement. MoveFile Table http://msdn.microsoft.com/en-us/library/aa370055(VS.85).aspx Edit - I just noticed that you are using InstallShield Express edition. In this case the MoveFile Table option is not available because Express does not have the capability of editing MSI tables directly. This means you will need to use a custom action to accomplish this objective. ... View more

I am not familiar with Add-in Express, but I suspect that you can register the plug-in by marking the DLL files for it as Self-Register or Extract COM Information. If the plug-in is .NET then you may need to instead select the .NET COM Interop option. Basically, it would help if you clarified what steps you would manually take from a command prompt to register/install the plug-in. If it involves registering the DLL with regsvr32 or using InstallUtil, then one of the above steps should work. Regards, Ajay ... View more

John, One way you could address this situation is to edit the InstallShield Express project file (.ise) with Orca and add the missing entries to the CreateFolder table. Just make sure to keep a back-up copy of the Express project file before making any changes to it because you could accidentally make an incorrect change leading to a corrupt project file. Modifying data in the Express project file directly with Orca can lead to a damaged project file so this should generally be avoided. But I believe it will resolve the issue that you are currently experiencing. Regards, Ajay ... View more

Well it depends on what type of script you are trying to create/edit. In a Basic MSI project you can create InstallScript custom actions under the Behavior and Logic - InstallScript view. You can also edit script for VBScript and JScript custom actions in the Behavior and Logic - Custom Actions and Sequences view. You can edit SQL Scripts in the Server Configuration - SQL Scripts view. Good luck with your script editing! ... View more

I believe that you are running into a limitation of Windows Installer user interface. According to the ControlEvent table doc it isn't possible to perform any actions from a ComboBox control: "On Windows XP or earlier operating systems, users can publish a control event only by interacting with a Checkbox Control or Pushbutton Control. With Windows Server 2003, users can publish a control event only by interacting with a Checkbox Control, SelectionTree Control, and Pushbutton Control. Listing other controls in the Control_ field has no effect." ControlEvent Table http://msdn.microsoft.com/en-us/library/aa368037(VS.85).aspx One workaround option is to create a PushButton control and label it something like 'Refresh'. Then when the user clicks on the Refresh button you can have a NewDialog event to go to the cloned dialog which will have the refreshed ComboBox controls. Hope this helps. ... View more

It appears that setup.exe doesn't have a special installation mode command line argument to instigate a MSI repair operation. So it will be necessary to accomplish this with command line parameters directly to msiexec as in the following command line: (silent repair) setup.exe /v"REINSTALL=ALL REINSTALLMODE=omus /qn" (basic ui repair) setup.exe /v"REINSTALL=ALL REINSTALLMODE=omus /qb" You can modify the value of REINSTALLMODE to control what is reinstalled during the repair. Also note that no MSI ProductCode should be passed in. This is because setup.exe will use the MSI file that it is associated with (via setup.ini). REINSTALLMODE Property http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspx ... View more

I understand that having two different installers for 32-bit and 64-bit installations is not what you want. However, unfortunately, it is required for Windows Installer installations. There is a global MSI file setting called Template Summary which indicates whether the package is a 32-bit or 64-bit package. This setting has to be 64-bit in order for the install to install to 64-bit locations and to run 64-bit script custom actions. Please look at the following supporting documentation: Windows Installer on 64-bit Operating Systems http://msdn.microsoft.com/en-us/library/aa372855(VS.85).aspx ... View more

It isn't clear to me why your assembly is not successfully installing to the GAC. I suggest you look into the following things to troubleshoot this behavior: 1. Verify that the assembly is the keypath of its component (You already indicated that the destination was GlobalAssemblyCache which is good). 2. Verify that the information in the MsiAssembly and MsiAssemblyName tables look correct for your assembly. Consult the table documentation for this. 3. Verify that you can manually install your assembly to the GAC on your test machine (without using MSI). 4. Does your assembly have any dependencies? If so, then maybe try a test where the dependencies are already installed to the system before beginning your MSI installation. 5. Although I don't think it matters for GAC installation, verify that the correct version of the .NET framework is being pointed to for Regasm.exe and InstallUtilLib.dll locations in Tools - Options - .NET tab. ... View more

You may want to look into the LaunchApplication InstallScript function. It is capable of launching other applications and scripts. You may also want to take a look at the SQL Scripts functionality in InstallShield. This will allow you to run SQL Scripts against MS SQL Server, Oracle, or MySQL. It also has a built-in dialog for getting connection credentials from the user. LaunchApplication http://helpnet.flexerasoftware.com/robo/projects/installshield16langref/LaunchApplication.htm SQL Scripts View http://helpnet.flexerasoftware.com/robo/projects/installshield16helplib/SQLServer.htm ... View more

SETUPEXEDIR property is set on the command line to msiexec.exe by setup.exe when the install is run through the setup.exe. This is why this property is undefined when the install is run directly from the MSI file. You may want to use the SourceDir property instead. This is a MSI property that is set by the ResolveSource action. So this means you can use the value of this property to determine the MSI location anytime after ResolveSource action. Note that by default InstallShield puts a condition on this action so that it is only run during a first-time install. SourceDir Property http://msdn.microsoft.com/en-us/library/aa371857(VS.85).aspx ... View more

It is possible to install to pretty much any folder on a machine including the Firefox installation directory. Hopefully, there is some Firefox registry value that indicates the install location of Firefox. If so, then you could use a System Search to obtain the install location from this registry value. Then you could use a Set Property or Set Directory custom action to set the install location of the file you are including with your install to point to the Firefox installation location. If Firefox installs to one of only a few install locations, then you could also create one system search to look into each such install location for the main Firefox executable. This could be another way to find the installation location of Firefox. Hope this helps! ... View more

It is very possible to do what you describe. It is possible to set public properties (properties whose name is in all capital letters) on the command line to msiexec.exe (if directly running from MSI) or setup.exe. For example: msiexec /i MYPROP1="my value" MYPROP2=test OR setup.exe /v"MYPROP1=\"my value\" MYPROP2=test" Now all you need to do is condition your custom actions based on public properties, and you are all set. ... View more

You may want to consider just right-clicking each file in the InstallShield IDE and selecting the Self-Register option. This way you would not have to create any custom actions yourself to handle this. You can also select the option to extract COM information from these DLLs instead of Self-Register. This option can be set in the Components view. ... View more