I see the same behaviour on 17.3. I even see that there is no TestODBCConnection action any more to pick from the "Add Custom Action" dialog. As we just upated to have another issue fixed, this stopps our complete deployment chain.
lets assume I have custom actions that needs to be run on every button click during the "Wizard Dialogs Stage" ("Next", Back", "Cancel"). Is there a smart way to hook the action to the buttons without adding it to every button in the Dialogs editor?
Hi Everyone, this one is going to get a bit tricky. Assume you want to deliver files based on user's decision. So I add a new feature via Organizations and add a condition to it. Organizations.png Next I add a checkbox to a dialog, so that the user can decide if the feature shall be installed or not...
I realized tha somehow I was able to to change the property, selected another dialog and when I switched back the property was reset. So my property change was never saved. After a few tries I was able to save it and it works as expected.
I just realized that an Edit Box is limited to 252 characters. Changing the property Text {260} to anything bigger does not change this behaviour (AI 16.3).
Any ideas if this can be enhanced?
I would like to go the other way. I have older MSI projects and would like to add the behaviour to prevent using the *.msi by the user. Just compiling the projects with AI 14.5.2 does not add the feature.
Hi Advanced Installer support team, when I am setting up a predefined MSSQL database connection to run some queries, I am not able to set a connection port. The field stays static on "automatic" and is not changeable. But the automatic port recognition does not work if the port is diffferent to the ...
Hi Everyone, I just stumbled upon something weired. 1. Build a custom action to execute the following inline script code: targetPath = "Hello World!" 2. Run the installer -> the action will fail. 3. Rename the variable to any other name -> The installer will execute the action without a problem Are ...
Hi Everyone, when I use the "Test ODBC connection" action with the SQL server driver (Driver=[\{]SQL Server[\}];Server=[SERVER_PROP];Port=[PORT_PROP];Uid=[USERNAME_PROP];Pwd=[PASSWORD_PROP];) then the connection is always tested via the instance name instead of the port. Even more, the port is ignor...