Hello and welcome to Advanced Installer forums, May I ask why you are not using our predefined support for prerequisites (which I believe is much easier to configure than a LaunchFile custom action)? Now, to answer your question, depending on the time when you try to install the prerequisite, the ha...
Hello, I have done some further investigations about this and I think I found a workaround that will help you avoid creating a database at install time. Please go to "SQL Databases" page --> your predefined connection --> in "Database" field, please insert a property that resolve...
Hello, I have further discussed this with our developers and unfortunately this is not on our upcoming future roadmap. Thank you for your understanding. However, as I have forgot to mention in my last thread, you can maybe try to use our "Slideshow" support. Hope this helps somehow. Best r...
Hello and welcome to Advanced Installer forums, This is happening because a normal MSI does not support such metadata. For more information about this, please have a look on the following Summary Information Stream Property Set article. However, our .EXE allows several new metadata, such as the &quo...
Hello Pieter, Could you please try to replace the SOURCEDIR property with SourceDir and see if that helps? The latter ( SourceDir property ) is the predefined Windows Installer property, while the latter is proprietary to us. After doing so, please rebuild your project and retest this scenario on a ...
Hello Jenelle, From what I understand here, you would like to get the version attribute from an executable and, based on that version fail the installer (please correct me if I'm wrong). Unfortunately, we do not have predefined support for such a task. However, we can achieve this through a custom a...
Hello Mike, This is quite strange, as the "/SetVersion" command should automatically change the ProductCode, as long as you do not specify not to by using the "-noprodcode" additional parameter. For more information about this, please have a look on our "Set Version Command ...
Hello Jaime, In order to create a patch for a .EXE file, you will need to extract the .MSI from both the upgraded and old version and use those in order to create a patch. Here are few things you should keep in mind while doing this: create a new version of your .EXE file by increased its version, b...
Hello Dov and welcome to Advanced Installer forums, Please note that we offer such a dialog as a predefined dialog. In order to add it to your project, please go to "Dialogs" page --> select "WelcomeDlg" --> "Add Dialog" button from the ribbon --> "OptionalFeatsDlg...
Hello Steve and welcome to Advanced Installer forums, Indeed, as you have mentioned, the list of drivers is taken from your machine. You can see a comprehensive list of your installed drivers by making use if the "ODBC Data Source Administrator" (odbcad32.exe) tool --> "Drivers" ...