I'm trying to figure out if it is possible, through the Automation interface, to set a Directory entry/value. We have some side-by-side installers which install to a path which incorporates the ProductVersion value; INSTALLDIR is defined to the parent folder so that side-by-side versions can NOT overwrite one another. For a better understanding, the resulting disk folder is intended to look like this:
At runtime, we employ a custom action which sets VERSIONDIR to "[INSTALLDIR][PRODUCTVERSION]\", which does work.
However, I would much rather modify the Directory value of VERSIONDIR prior to the build, via Automation. In other words, the raw directory table entry in the ISM file currently looks like this:
what you are describing should work provided that INSTALLDIR has been defined at the point you try to assign it.
I have done something similiar where I read in a registry value and drop a directory into a given location based on that registry value that is assigned to a property that corresponds to a folder location.
what behavior are you seeing when you try to do this?
The Automation interface already has a mechanism for revising INSTALLDIR. However, I am not trying to revise INSTALLDIR, but one of the other entries in the Directory table - in my example the one called VERSIONDIR. So far I have been unable to find a way to revise any user defined entry in the Directory table, hence this conversation thread.
To re-iterate from my original post:
I would much rather modify the Directory value of VERSIONDIR prior to the build, via Automation.
If there is absolutely no way to do this, I'll have to stick with the run-time Custom Action solution I am using.
