Does anyone know howto get the destination path for a enumerated file in the MEDIA ???
My setup use dynamic file linking and script defined destination paths.
I would like to use something like the old COMPONENT_FIELD_DESTINATION, but I cant find anything similar anymore in InstallShield.
Alternative if anyone know how to get a list of what files that was actually moved during filetransfer.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Howto get dest path for a enumurated file ???
Started by
vuttex
, Sep 09 2008 14:49
3 replies to this topic
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 09 September 2008 - 15:25
Look up the name of the directory table entry for the component (it's in the component's destination settings in curly brackets). Then you should be able to get the value of this property at runtime using MsiGetProperty.
Stefan Krüger
InstallSite.org twitter facebook
vuttex
-
- Full Members
- 35 posts
Posted 09 September 2008 - 16:27
Im not sure this is possible in my case. Maybe you can provide some more information if I describe my project some more.
The project is a InstallScript MSI.
The file linking is dynamic with lots of "sub-folders" and I dont know what files that are included. Could be one file or hundreds. The "head" component is a script defined folder. I set the path in my script.
As far as I can tell every "sub-folder" is considered to be component when you run the setup. But in the Directory Editor I will only see the "head components".
I do a FeatureFileEnum first for all components and then for all files in each component. This work ok, a bit slow when many files are included. Then I would like to compare my file list from the MEDIA with the files on the target machine to do a compare, version, date etc.
What do you think I will get when calling MsiGetProperty on the runtime components ?
I would like to get the full dest path not the "head" components dest path. Because then it will not be the dynamic setup I wanted.
The project is a InstallScript MSI.
The file linking is dynamic with lots of "sub-folders" and I dont know what files that are included. Could be one file or hundreds. The "head" component is a script defined folder. I set the path in my script.
As far as I can tell every "sub-folder" is considered to be component when you run the setup. But in the Directory Editor I will only see the "head components".
I do a FeatureFileEnum first for all components and then for all files in each component. This work ok, a bit slow when many files are included. Then I would like to compare my file list from the MEDIA with the files on the target machine to do a compare, version, date etc.
What do you think I will get when calling MsiGetProperty on the runtime components ?
I would like to get the full dest path not the "head" components dest path. Because then it will not be the dynamic setup I wanted.
Stefan Krueger
-
- Administrators
- 13,269 posts
InstallSite.org
Posted 09 September 2008 - 17:36
| QUOTE |
| The file linking is dynamic |
Sorry, I missed that bit in your original post. In this case my suggestion won't work.
| QUOTE |
| with lots of "sub-folders" |
Don't do that, it will result in inconsistant ComponentId GUIDs. You should at least create components for each sub folder.
[$componentkey] is the value of the install directory of the component, with the value componentkey used as a key into the Component table. You would have to get the list of components at install time using some installer SQL commands.
[$componentkey] is the value of the install directory of the component, with the value componentkey used as a key into the Component table. You would have to get the list of components at install time using some installer SQL commands.
Stefan Krüger
InstallSite.org twitter facebook