Noober Setup question
Absoloutely new to packaging. Company has just boutght wise packaging studio V8 and Client Management suite V7. I have no problem with straight forward MSI apps but I have an app which must be run from setup.exe - it looks as though this calls the app.msi and goes through the install. If I try and run the app.mis it says setup.exe must be run first. I tried setup /? and it says I can use /S for silent install - this doesn't work. any ideas where I would start on this !!
Cheers
J.
Cheers
J.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
...or even ISSETUPDRIVEN.
If that proves not to be the culprit, run the MSI through WPS's debugger. You'll see straight away what triggers the message.
If that proves not to be the culprit, run the MSI through WPS's debugger. You'll see straight away what triggers the message.
Posted by:
Joebhoy
13 years ago
Damn! I dont think you realise how noob am I :-) will do a search cheers.
p.s. my wps doesn't have a debugger on it!
J.
p.s. my wps doesn't have a debugger on it!
J.
Posted by:
anonymous_9363
13 years ago
my wps doesn't have a debugger on itReally? Wow! They're sending out personalised versions now?
Hit 'F1', type 'debug', press Enter.
BTW, if you're that new, before you even start WPS again, get hold of Phil Wilson's The Definitive Guide to Windows Installer.
Posted by:
Joebhoy
13 years ago
cheers for the book tip. Will have a look. Already tried the 'search' for debug. Nothing came up.
Cheers
Joe.
Cheers
Joe.
Posted by:
cygan
13 years ago
get your company to give you the proper training you need or they may regret in the long term not doing that
Posted by:
rock_star
13 years ago
if SETUPDRIVEN= 1 doesn't work ..
then look for the parameters that are passed to msi .
setup is a exe that call's msi so if msilogging is enabled in your system.,
during installation u will log generally kept in %temp% folder.
and look for property that are passed to msi .
so when u get the properties pass those and run msi along.
wisely said...
then look for the parameters that are passed to msi .
setup is a exe that call's msi so if msilogging is enabled in your system.,
during installation u will log generally kept in %temp% folder.
and look for property that are passed to msi .
so when u get the properties pass those and run msi along.
get your company to give you the proper training you need or they may regret in the long term not doing that
wisely said...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.