Modifying INSTALLDIR in a custom action, component dirs not updated
Greetings Everyone,
I have run into a problem where we determine where our installation is going to go based on some evaluation in an InstallScript Custom Action. Within this action the [INSTALLDIR] property is updated.
When running the installation the base files are put in the correct location but all of the components which reside in folders within the INSTALLDIR are placed in the default INSTALLDIR and not within the updated INSTALLDIR. All of these components reside within the main app feature and their destinations are set to [INSTALLDIR]folder\ but it seems that it uses the default INSTALLDIR and NOT the updated one even though the base application is installed to the updated INSTALLDIR.
I am using an IS custom action for immediate execution. I also tried creating separate features for each component with no resolution.
Setting those component destinations to [INSTALLDIR]something sounds right. Perhaps post the custom action type/code/settings, and someone here might be able to help?
