I have this re-occuring package which currently uses a vbscript to copy files from a directory which the package installs to the MS Office directory (the script figures this out through a registry key).

Depeneding upon the version of Office, the script will copy files from one directory to a directory within the office directory.

I'd like to use the MoveFile table to do this instead but I'm not quite sure where to start. I have to determine the version of office being used before the file move occurs.

Is there a doc on how to do this?

Thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I guess you could use AppSearch to set a property (or a bunch of properties, depending on how you want to handle things) and then use the property as the directory name in the MoveFile table.
Answered 06/08/2011 by: VBScab
Red Belt

Please log in to comment
0
I've used the search option and am placing into variables. When you use the Move File Table, it doesn't seem as if I can use those variables. How can I apply those variable to the move file table? I tried adding them directly to the table but that doesn't work.
Answered 06/13/2011 by: Secondlaw
Third Degree Blue Belt

Please log in to comment
0
Not variables, properties :-)

In place of the folder names, use the property names enclosed in square brackets, e.g. [MyTargetFolderName]
Answered 06/14/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

Not variables, properties :-)

In place of the folder names, use the property names enclosed in square brackets, e.g. [MyTargetFolderName]


In place of the folder names, use the property names enclosed in square brackets, e.g. [MyTargetFolderName]

Yes, of course. This is what I've tried. If for example I go to the MOVE FILE table, I can manually insert my property as you've mentioned [OFFICE2KDIR]. Now if I go back to the gui, it doesn't seem to accept the setting I've given it (possibly because it doesn't exist yet?). I thought I would be able to see this in the GUI.
Answered 06/14/2011 by: Secondlaw
Third Degree Blue Belt

Please log in to comment
0
"the GUI"? Is this InstallShield AdminStudio? Wise Package Studio?
Answered 06/14/2011 by: VBScab
Red Belt

Please log in to comment
0
I don't get what your package does?

It install files to an office directory and then from there using the VBS, copies these files from this directory to another office directory based on the Office version (Office11,Office12) I presume.

I'm not sure if this may help, you can have the AppSearch to create property (OFFICE12) based on the Office12 destination path and then in the Component for Office12 for example, include this property in the Condition entry. Do the same for other component (Office11) as well. This of course helps if different files are copied for difference office versions.
Answered 06/14/2011 by: PackageExpert
Blue Belt

Please log in to comment
0
Sorry VBScab - WPS 8.

Package Expert - The files being copied are being copied from another folder. Depending upon the version of Excel found, the files will be copied to that directory.

Example:

Copied from:
C:\Program Files\Mysoftware\copythis\*.*

to
[EXCELVER]\copythis\
Answered 06/15/2011 by: Secondlaw
Third Degree Blue Belt

Please log in to comment
0
It looks like another "feature" of WPS. Even if you seed the property with the path to an existing folder, the GUI doesn't reflect it.

As long as the install works, ignore the GUI's lack of intelligence. Annoying, though...
Answered 06/15/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

It looks like another "feature" of WPS. Even if you seed the property with the path to an existing folder, the GUI doesn't reflect it.

As long as the install works, ignore the GUI's lack of intelligence. Annoying, though...


Unfortunately, this does not seam to be possible. I can see the property value change in the log file but you cannot use it as a directory placeholder. That at least is my observation. There's gotta be a way to do this. Why such a limitation?
Answered 06/16/2011 by: Secondlaw
Third Degree Blue Belt

Please log in to comment
0
Check out the MoveFile table
As you can see the SourceName column field can hold wildcard(s) and * would suite you fine.
For the DestFolder column field I would use a Set Property custom action which you populate with the correct (version) path.
Answered 06/16/2011 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity