I want to call setup.exe through blank msi. That setup.exe resides in my sourcefolder. I am using Wise Package Studio, i am new to packaging.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity



is your setup microsoft or instsallshield
what command line switches are you using
Answered 07/29/2009 by: cygan
Fifth Degree Brown Belt

Please log in to comment
it is very confusing. [:o]

I do not know these many concepts. Please tell me which option will i have to select? and i want to run it from sourcedit, not from installed files
Answered 07/29/2009 by: taniya
Senior Yellow Belt

Please log in to comment
open your .wsi project, Go to MSI Script
Installation Mode : All Custom Action

In the action list, select one of the following :
Execute Program From Destination (Select this if you want to execute the setup.exe from a folder locally)
Execute Program From Installation (browse for your setup.exe, it will in the .msi temp folder during installation)
Execute Program From Installed File (setup.exe must be in your project)
I think "Execute Program From Installation" is the best case.

Detail Panel
Custom Action Name: Specify the custom action name
Exe file : Browse for your setup.exe
CmdLine : insert any command line if neccessary

Location :
Uncheck No Sequence
Sequence : Normal Execute Immediate/Deffered
Put your custom action anywhere you like in the sequence. If your want to execute the action at the end, put it right before InstallFinalize and click Add
Condition : If you want this custom action to be executed during installation only, type : NOT Installed

Properties Panel
Processing : Synchronous, Ignore Exit Code
Schduling : Always Execute

Another thing, check this link : http://itninja.com/blog/view/appdeploy.com->-training-videos->-custom-actions-with-wise-package-studio
Answered 07/29/2009 by: darkfang
Blue Belt

Please log in to comment
If you are new to packaging and have Wise Package studio available to you, perhaps you should be asking a different question.

My first question to you is why do you want to install a setup.exe from an MSI? There are valid reasons, but using an MSI as a wrapper is not one of them. If the setup.exe is the installation file, you have plenty of options other than the one you suggested.You could repackage the installation into an MSI (preferred), or you could automate the installation with a respose file if the setup.exe supports it.
Answered 07/29/2009 by: elgwhoppo
Senior Purple Belt

Please log in to comment
Answered 07/30/2009 by: sourav
Orange Senior Belt

Please log in to comment
No disagreement here. Also, 'taniya', are you sure that the set-up stub doesn't contain an MSI already? To find out, clear out your %TEMP% folder (note: not %SystemRoot%\TEMP). Then run the stub but stop at the first screen, normally 'Welcome to [whatever lame product it is]". Check your %TEMP% folder for an MSI. If there's one there, copy it somewhere, rename it to something sensible (it will have been created with a randomly-created name in %TEMP%) and use that. To make changes to its actions, use a transform: you should never edit vendor-supplied MSIs.
Answered 07/30/2009 by: VBScab
Red Belt

Please log in to comment