Hi,
INSTALLDIR always has a value from what I have experienced. If the registry value is present, INSTALLDIR has the folder path (ex: C:\install the application here.) If the registry value is not present INSTALLDIR has the value C:\APPDIR. Wouldn't testing INSTALLDIR by itself always be true since it always has a value?
Can you please attach a basic test .AIP project that proves the results of this test case?
As described in the
user guide reference, the value of any search name public property will be
NULL if the registry location does not exist.
FYI: Our support team usually references the user guide in blue text, thus all inline links from this post are relevant.
I am assuming you need the search result to set the APPDIR at install time. In this case you will be interested in setting the APPDIR property after the
AppSearch standard action using a
Property set with Formatted custom action. Since you are using a path from the registry, you might also want to
conditionally display the FolderDlg dialog depending on whether or not you have the registry value containing the path.
Also,
here's a similar post with a sample project attached from my colleague Gabriel.
Please forward this thread to someone who can implement our suggestions and let us know how it turned out.
All the best,
Mihai
FOLLOW US
Get the latest news in Application Packaging