And this is the whole problem: I don't know exact property name to read at compile time, it is determined in runtime based on other properties. Here is an example:
Now I understand how AI_LISTBOX_DATA works. I eventually split listboxes in different dialogs. My approach now is as follows:
1. Have UI sequence script which pre-calculate all listboxes at wizard launch and store them in temporary property 2. In dialog initialization actions, copy value from temp ...
Thanks for your response! This is a very unfortunate behavior. The problem is that both listbox population logic share a lot in common, just slight differences and splitting them into separate scripts will cause a lot of duplicates and will be hard to maintain.
Catalin, thanks for your response it explains some of my observations during testing. But I have a couple of other questions related to this.
Ok, Advanced Installer tool is per-machine and requires administrator permissions to install it. Then, I would expect the following workaround to work, which ...
We are using Advanced Installer to build installers using Azure DevOps and generally it works like charm!
However, we found a problem when we moved from cloud-hosted to self-hosted agents, when we run build agents on our VMs. We use least privilege principle and didn't grant the agent account ...
This is very unfortunate behavior. Major upgrade strategy for smaller products is the most convenient way to update the product.
And for many aspects in AI it is possible to define task execution conditions. Services are not changed often even during major upgrades. Service executables -- they may ...
disclaimer: I'm not an AI support, just random user of AI
Custom PS scripts aren't encrypted, they are encoded and you can easily recover the script using PowerShell. Copy encoded string from XML tag value to clipboard, then in PowerShell console insert copied base64 string:
Our application installs the Windows service along with install process. By default we configure the service to run under "Network Service" account, it is configured in AI project.
However, we treat this as default installation and recommend (though not requiring) customers to use gMSA service ...
That probably happens because you have changed the ProductCode property and now Windows Installer sees your MSI as an upgrade. this may happen since we use Azure DevOps pipelines to build the MSI. It appears it re-generates the product code every time ...
We have an MSI package which includes custom actions executed during install and uninstall to configure certain things on install and roll back on uninstall. However we detected a major flaw in custom action script executed on uninstall.
My aim is to fix the MSI (only custom action, all other ...