HI,

I create a standard repackage MSI with WIse. When i launch the install, if i want to perform some PRE install (move a folder, copy a file, set a CACLS on a specific foler) on the wks prior to the main installation, how would you suggest to achieve this?

And right after the main install, if i want to perform some POST install (again, move files, copy flag files, CACLS, etc..) How would you suggest to do this again?

Thanks for your suggestions.

Bob
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
You can do all of that activity within the MSI itself.
Answered 09/18/2008 by: VBScab
Red Belt

Please log in to comment
0
To add on this, if i want to run something not supported by wise (personnal .exe file) is it possible to execute it at the beginning ? before the file copy ? but my "personnal .exe file" must be part of the msi. any thought?
Answered 09/18/2008 by: princecraft
Orange Belt

Please log in to comment
0
ORIGINAL: princecraft

To add on this, if i want to run something not supported by wise (personnal .exe file) is it possible to execute it at the beginning ? before the file copy ? but my "personnal .exe file" must be part of the msi. any thought?

If you don't want to leave the file behind after the installation has finished I would use a "Custom Action Type 2" (This custom action calls an executable launched with a command line.) and sequence it just before the InstallFiles action.
Answered 09/18/2008 by: AngelD
Red Belt

Please log in to comment
0
ORIGINAL: princecraft
To add on this, if i want to run something not supported by wise (personnal .exe file)
What does THAT mean, 'not supported by Wise'? Why would it care? A file is a file is a file...
Answered 09/19/2008 by: VBScab
Red Belt

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