Hello


We are required to make the MSI packages in a way so the destination folder can easily be altered in the future. What is the best way to do this in the case of REPACKAGING.

For example: after snapshotting, let's say, Java SDK software, Wise Package Studio will provide every file installed (and every registry value reffering to files installed) with a hardcoded path. So I guess we have to replace that hardcoded path with a variable (property)...?

Anybody give best practice advice please...
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
Wise usually replaces any paths it finds (and recognises) within the registry an ini files with variables. It will not always be 100% effective in doing this because the paths can be in an unrecognised format (eg:double or forward slashes) or the paths may be held elsewhere (eg: cfg files).

INSTALLDIR is the public property that is normally used to determine the installation path.
Answered 01/05/2006 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
You can specify your INSTALLDIR from the command line on installation:

msiexec /i <YOURAPP.MSI> INSTALLDIR=<YOURPATH>
Answered 01/06/2006 by: xythex
Orange Senior Belt

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