View Full Version : Adding components via automation doesn't use path variables

Tony Patterson
11-23-2004, 03:57 PM

I am adding a lot of components to a feature using the automation interface. But they don't seem to be picking up the Path Variable that I have set.

The PV is something like this X:\Site\QA\V4.03\INTRA\
But the files source path comes out like this X:\Site\QA\V4.03\INTRA\filename.exe
not <Site>filename.exe as I would expect.

The documentation for ISWiFile.FullPath says :
"Stores the fully qualified path (including the file name) of the file's source location. Any path variables are resolved to the actual path."

What is the actual path?


12-14-2010, 05:52 PM
Looks like this is still happening even with InstallShield 2011's automation interface. Would be nice to have automation added files use path variables. Maybe I'm missing something that would enable this though.