First I read a value into property from a registry key, via an the Search section.
If that property now has some content I need to modify it to add the Windows folder path to the start; so I add "Property Set with formatting" action to modify the property:
PLUGIN_DIR
[WindowsFolder][PLUGIN_DIR]
But no matter what Custom Action I put this into, it never happens. Logically it should go into AppSearch, but if custom actions happen before the msi's own (and I can't see anywhere in the help that says when Custom Actions happen with respect to the build in ones), then it could go into LaunchConditions or CostInitialise - but it make no difference.
I have tried adding ErrorMessages everywhere and they never happen either.
All that happens is I get a "Could not access network location" error during the CostFinalise phase because it is trying to reference the file using the partial pathname.
I'm probably doing something wrong, so I'm quite prepared for someone to point and go "it's easy"!
I hate to sound like I'm complaining but Advanced Installer seems to make everything much, much harder than it needs to be - I can do all this in seconds in our non-MSI installer product.
FOLLOW US
Get the latest news in Application Packaging