I want to be able to retrieve the msi package name. If there is an easier way to do this other than trying to use MsiSourceListGetInfo, I would appreciate it. Here are the pertinent code pieces I have included in setup.rul to try to use MsiSourceListGetInfo //////////////////////////////////////////////////////////////////////// #include "ifx.h" #include "iswi.h" #include "isrt.h" #define MSICODE_PRODUCT 0x00000000L // product code provided #define MSIINSTALLCONTEXT_MACHINE 4 prototype NUMBER msi.MsiSourceListGetInfo(BYREF STRING, BYREF STRING, NUMBER, NUMBER, BYREF STRING, BYREF STRING, BYREF NUMBER); function myfunction() ... ... begin szProductCode="{3251536B-F670-4C69-B5E9-36697BE36617}"; szUserID=""; nContext=MSIINSTALLCONTEXT_MACHINE; nOptions=MSICODE_PRODUCT; szProperty=INSTALLPROPERTY_PACKAGENAME; nReturn = MsiSourceListGetInfo(szProductCode, szUserID, nContext, nOptions, szProperty, szValue, nValue); ... ... end; Everything compiles ok, but when I run it, I get an error message saying it failed to find the dll function. Do I have to include the MSI.dll and use UseDLL and UnUseDLL? ... View more

I have two basic msi projects. I build each and install them. I rebuild each project with a new package code generated. I run them. On one project I get the upgrade message and when I respond that I want to continue with the upgrade, I get the SetupResume dialog. On the other, I do not get the upgrade message, it goes right to the SetupResume dialog. Why the inconsistent behavior? Is the second really doing an upgrade? ... View more

In the MSI commandline parameter section of the setup.exe tab in releases, I provide a path (C:\Mylogfilepath\install_log.txt) where I want the log file created. If C:\Mylogfilepath doesn't exist when setup.exe is run, I get an error message. If I create C:\Mylogfilepath prior to running setup.exe, everything is good. Is there a command line parameter that forces the creation of the folder if it doesn't exist or is there some other mechanism to verify that C:\Mylogfilepath exists at runtime so the user doesn't get an error message? ... View more

I have a basic msi. I have a combo box that is enabled and visible. It is tab stop enabled and is set to tab stop 0. It is populated with text items and interger values. I have property is integer set to true.The property is SELECTEDMODULE. It is in the Property manager. I have a custom action that sets SELECTEDMODULE = 1 just prior to displaying the dialog. The dialog displays, the combo box is visible and the text associated with SELECTEDMODULE=1 is displayed ok. I hit the Next button to go to the next dialog . I am not modifying the SELECTEDMODULE property. Then I select the Back button. I return to the dialog with the combo box, but the combo box is not visible. If I pass my mouse over it, The combo box appears with the item for SELECTEDMODULE=1. I can also get the combo box to appear if I hit the tab key. Why is the combo box hidden on the back event? ... View more

I have a basic msi project with 2 features: Feature1 and Feature2. When the customsetup dialog is displayed after InstallWelcome, the selection tree shows Feature1 on the first line and it is highlighted. Feature 2 is displayed on the second line and it is not highlighted. I want a mechanism to display the customsetup dialog showing Feature1 on the first line in the selection tree unhighlighted and show Feature2 on the second line and it is highlighted. I cannot determine if there is an event, subscription, or condition that would permit this. Can anyone shed some light on this? Thanks in advance. ... View more

I have a basic msi. I have added a text box to the InstallWelcome dialog with the text field set as MYPROP=[MYPROP]. I run the following command: setup.exe /v"MYPROP=abc" When the InstallWelcome dialog is displayed, I see MYPROP= I would expect to see MYPROP=abc When I perform the same steps, setting INSTALLDIR=abc on the command line and setting INSTALLDIR=[INSTALLDIR] on the InstallWelcome dialog, I can see the value I passed to INSTALLDIR on the command line. I was under the impression setting command line properties overrode all other properties except those set by the operating environment. At what point in the UI or Execute sequence are properties set on the command line available for use during the install? ... View more