Hello Pieter,
First of all, please accept my apologies for the delayed reply, but we were quite busy lately and we also started working from home as of few days ago.
In what regards this, I'm sorry to hear that changing the property did not help.
Unfortunately, I really can not say why this happens as this is a really strange behavior which I do not believe is related to Advanced Installer (as the action that writes the registry values is a
standard action, not a custom one - i.e. created by us).
As of today, I have retested the project you have sent me by stripping it down and building it, then launching it from both a normal location and from a network one.
In this scenario, I could think of two things we can try:
1. Try to substitute the SOURCEDIR property. For instance, have a
"Set Property"custom action (with sequence) that sets another property to the value of SOURCEDIR and place that at the beginning of the
"Install Execution Stage". After doing so, use that property to write the registry.
2. If the above does not work either, I am afraid that the only thing left would be to achieve this through a
custom action. For instance, we can have a script that writes the registry for us. In order to fully mimic the default behavior, this custom action should be added as a custom action with sequence and scheduled in
"Install Execution Stage" -->
"Add resources" action group --> between
"WriteRegistryValues" and
"WriteINIValues" standard actions.
Hope this helps somehow.
Best regards,
Catalin
FOLLOW US
Get the latest news in Application Packaging