/build/static/layout/Breadcrumb_cap_w.png

Repackaging Process

i have a question on repackaging process

if an application has a dependency. For Ex. Like a access database file. Access is not a part of my base load.

there are two processes

Process One

1. install the pre-req (here MS Access).
2. then run the pre install capture.
3. install the leagacy application.
4. run the post install capture.

OR
Process Two
1. test if the application is working on one test machine with the pre req installed.
2. then take another clean machine with no pre req installed.
3. run the pre install capture.
4. install the leagacy application.
4. run the post install application.

Which is the exact process to be followed ?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: SteveBA 20 years ago
Senior Yellow Belt
0
If the application installs without complaining about Access not being installed then go for "Process Two"

But, what would be a good idea (for your own experience and knowledge) is to try both methods and see how much difference there actually is between the resulting packages.

Not a definitive answer I know but best to have a clean a machine to start with.

Steve.
Posted by: bheers 20 years ago
Second Degree Blue Belt
0
i usually follow the first process, there is a debate as to which process is the best,
if we use process 2 then some of the registry keys may not be caputred or some of the files which actually get created when the application is launched . the files/registries do not get created cuz the application cannot launch as it depends on the pre req to launch.

my question here is which process is the best practice ?
Posted by: MSIMaker 20 years ago
2nd Degree Black Belt
0
As I said it depends on whether you can actually install the app without the pre req stuff.

I dont think there is a strict way to capture......anyone who only captures in one way isnt going to get the full story.

I capture with Winstall and WPS capture depending on the app. I also use SMS installer to verify captures sometimes. To capture InstallShield installs I start the exe and let it get past the installshield part and then start Winstall and capture the rest. I also like to do the post capture and then start another new capture and reboot during the second capture to make sure I got it all.

There really isnt a "perfect" way to do it for all circumstances...
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ