To capture or NOT to capture...
I have a request to package some applications with Wise Package Studio. The PM wants me to capture more than 1 application within the MSI to make the overall install time shorter since all the users will be getting same apps. My question is whether or not it is best practice to capture more than 1 application per-capture? If not, why?
My feeling is that I shouldn't be capturing more than 1 application per-capture because it would be easier to package and more importantly easier to troubleshoot if needed.
What do you guys think? Have you ever been asked to capture more than 1 application and if so, how did it go?
Thanks guys!
My feeling is that I shouldn't be capturing more than 1 application per-capture because it would be easier to package and more importantly easier to troubleshoot if needed.
What do you guys think? Have you ever been asked to capture more than 1 application and if so, how did it go?
Thanks guys!
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Can we have the PM's name, so that we all know to discount anything he might ever say in the future?
Here's an MSI:
App1
App2
App3
App4
App5
Have him explain how he's going to upgrade, say, App4. Or uninstall it. Idiot...(him, that is, not you!)
If all users are getting the same apps, they should be included in the workstation build.
Here's an MSI:
App1
App2
App3
App4
App5
Have him explain how he's going to upgrade, say, App4. Or uninstall it. Idiot...(him, that is, not you!)
If all users are getting the same apps, they should be included in the workstation build.
Posted by:
justinSingh
14 years ago
Actually what I was thinking! (couldn't get my thoughts put on paper.. or in this case post :P)
Btw, the PM name is Mark Leon. LOL
Hope no one tells him I mentioned his name. :-/
Btw, the PM name is Mark Leon. LOL
Hope no one tells him I mentioned his name. :-/
Posted by:
anonymous_9363
14 years ago
they should be included in the workstation build....but still delivered via MSI, of course.
Posted by:
AB
14 years ago
ORIGINAL: MSIPackager
Mark Leon is officially insane!
That sounds like the name of a FaceBook group...
Posted by:
t_claydon
14 years ago
Your right capture them seperately.
Problems will occur when you want to update one of the packages with a severvice pack because you'll have to recapture all the applications again and retest them all wasting loads of end user time in the long run.
If you have to you could nest them - that way it will look like only one package is being installed.
Problems will occur when you want to update one of the packages with a severvice pack because you'll have to recapture all the applications again and retest them all wasting loads of end user time in the long run.
If you have to you could nest them - that way it will look like only one package is being installed.
Posted by:
JillBA
14 years ago
We've put a script wrapper around ours, that reads a setup.ini file and in there we list [Package1], [Package2], etc, that way it keeps the MSIs separate and allows us to update them easily without affecting other apps.
When we first started packaging many years ago, we used to get PMs telling us to put them all in one MSI, but they soon got the message that it wasn't a good idea! [;)]
When we first started packaging many years ago, we used to get PMs telling us to put them all in one MSI, but they soon got the message that it wasn't a good idea! [;)]
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.