I'm needing to install files in specific locations that the user is free to change. The only real clue is that these folder names will be stored at known locations in the registry. I've found the
/AddRegLocator switch that can be used on a command line build. But, the example offered in the docs isn't incredibly illuminating...
Code: Select all
AdvancedInstaller.com /edit MyProject.aip
/AddRegLocator REG_SEARCH_RESULT -signature reg_search
-root HKLM -key Software\MyKey\
If I understand that correctly, the property name "REG_SEARCH_RESULT" could then be used in subsequent calls in the very same manner as the predefined variables (eg, APPDIR, WindowsFolder, MyPicturesFolder, etc) can be used? IOW, I could then do something like...
Code: Select all
AdvancedInstaller.com /edit MyProject.aip
/AddFile REG_SEARCH_RESULT D:\path\file.ext
Have I totally missed the point of this function, or is that essentially the way it can be used?
If I understood that part correctly, then I do have a couple of follow-ups...
* What's the point/signficance of the
<signature> parameter?
* Would I need to use the
-type LocatorTypeDirectory switch to use this as I would a pre-defined folder?
Thanks!
FOLLOW US
Get the latest news in Application Packaging