Launching exe and MSI part of my current MSI
Dear all
I am using Wise Package Studio 7.0 SP3, I am trying to do the following but it is not working.
My current install MSI (Vm2_Install) needs to launch 3 exes and 4 msi as part of Vm2_Install.msi. I have used "Execute Program from installation" for executable file and "Install MSI from installation" for msi BUT when I launch Vm2_Install.msi all the exes and msi launches at the same time but I want them in sequence.
Can some one help me how can I control to wait for my main MSI until 1st exe completes then launch 2nd exe or msi.
I am new to this and not a full time Package developer. :)
Many thanks in advance
I am using Wise Package Studio 7.0 SP3, I am trying to do the following but it is not working.
My current install MSI (Vm2_Install) needs to launch 3 exes and 4 msi as part of Vm2_Install.msi. I have used "Execute Program from installation" for executable file and "Install MSI from installation" for msi BUT when I launch Vm2_Install.msi all the exes and msi launches at the same time but I want them in sequence.
Can some one help me how can I control to wait for my main MSI until 1st exe completes then launch 2nd exe or msi.
I am new to this and not a full time Package developer. :)
Many thanks in advance
0 Comments
[ + ] Show comments
Answers (12)
Please log in to answer
Posted by:
timmsie
13 years ago
sounds like you've got you "Execute Program From Installation" CA's set to be Asynch
Have a look at the "Properties" tab on the custom action the "Processing" option needs to be Synchronous
But I'd agree with itolutions in your situation wrapping this stuff in an msi is overkill there's no need as you're not really interested in what Windows Installer offers you.
You'd be better off creating a vbscript or even a simple batch file.
Have a look at the "Properties" tab on the custom action the "Processing" option needs to be Synchronous
But I'd agree with itolutions in your situation wrapping this stuff in an msi is overkill there's no need as you're not really interested in what Windows Installer offers you.
You'd be better off creating a vbscript or even a simple batch file.
Posted by:
anonymous_9363
13 years ago
Avoid nested MSIs. You will run into problems with upgrades and patches in the future.
Either create a wrapper script/command file or EXE or use your deployment system.
Either create a wrapper script/command file or EXE or use your deployment system.
Posted by:
Ash786
13 years ago
This is one use only to setup the system. it is not for upgrade or anything. The aim is to run MSI once on the new machine to launch dependent application, instead of going on different paths to launch each dependent files. It is for in-house use only and not for client.
Posted by:
MarcusPiper
13 years ago
From everything I have ever heard about packaging..."NEVER repackage a vendor MSI"!
Perhaps if you let others know how you intend to deploy the package, they may be able to give you more specific help?
Perhaps if you let others know how you intend to deploy the package, they may be able to give you more specific help?
Posted by:
itolutions
13 years ago
1) Did you set "check exit code" flag (synchronous mode) for yours custom actions?
2) In complicated situations Executables can return exit code before installation completion. In this case you need to sequence additional custom actions to wait installation process completion. Like this:
2) In complicated situations Executables can return exit code before installation completion. In this case you need to sequence additional custom actions to wait installation process completion. Like this:
Function WaitForTermination(strProcess,iMaxWaitSeconds)
Dim objWMIService, colProcess, objProcess,currentSec, flag
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
currentSec = 0
Do while currentSec<iMaxWaitSeconds
//!!!!!!!some "one minute pause" function should be here!!!!!!!
Set colProcess = objWMIService.ExecQuery _
("Select * from Win32_Process WHERE Name='" & strProcess & "'")
flag = true
For Each objProcess in colProcess
flag = false
Next
If flag then Exit Do
currentSec = currentSec + 1
Loop
End Function
Posted by:
mazessj
13 years ago
Ian, we are frequently in sync. Many times when I read a post and have a gut reaction to reply, you've already posted what I was thinking. You are obviously a strong supporter of best practices.
Posted by:
mazessj
13 years ago
Ash,
Even more reason not to use an MSI. Just script/batch/sequence it instead. You're trying to shoehorn a tool that you shouldn't be using.
Even more reason not to use an MSI. Just script/batch/sequence it instead. You're trying to shoehorn a tool that you shouldn't be using.
Posted by:
Ash786
13 years ago
Many thanks to all of you, I have taken Mazessj advice and has created a batch file procedure and that is working fine.. Thanks for the Idea
Posted by:
mazessj
13 years ago
Heh [:)], sorry, I wasn't looking to take credit, just to reinforce your suggestion.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.