/build/static/layout/Breadcrumb_cap_w.png

Filtering a Setup Capture

Hello AppDeploy community!

I am seeking your advice on an issue I often run in. I'll use my current software as an example.

The Software requires .Net 2.0 SP2 to be installed which is fine and dandy, since we already have it packaged. So, before starting my Setup Capture, I install it without any problems. Reading a little around the forums, someone had suggested for another package that to make sure that the pre-reqs aren't in your Setup Capture, one thing you could also do was to install the software installation, and start the setup capture after the installation of the pre-reqs by the said software.

Tried it, but, when I capture my installation, I still get files in [Windows]\Microsoft.Net\Framework\v2.0.50727 and naturally, with that comes a nice boatload of registry keys that are probably useless to my package.

So, my question is, how do you guys go about handling such cases?

Would it be too brutal to delete [Windows]\Microsoft.Net\Framework\v2.0.50727 from my capture? If not, how could I know in that case the keys that I can safely remove?

Thanks for your input!

Stephane
Asked 14 years ago 2474 views
0 Comments   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 14 years ago
Red Belt
0
Install pre-requisites first, always. If you have enough disk space, there is an argument for having VM snapshots of different configurations of pre-reqs on. These days, most clients I work for are enlightened enough to provide packagers with machines having serious horse-power, meaning that installing pre-reqs beforehand isn't such a hassle, so I generally don't need to bother with the snapshot route.

As for .Net Framework, all flavours should be part of the base build and therefore always present on a packaging machine.
Posted by: Fau 14 years ago
Senior Purple Belt
0
Not denying anything of what you said there VBscab. In fact, I'm 100% behind you with that.

However, I'm still looking for an answer to the question since like I said, the pre-reqs are installed on my packaging machine, but they still get installed in my Capture. Was looking more for tips rather than a solution, if at all possible.

Thanks again!
Posted by: anonymous_9363 14 years ago
Red Belt
0
Your original post said that you began the capture after the installer had completed installing the pre-reqs, not that you had pre-installed the pre-reqs yourself (my emboldening):someone had suggested for another package that to make sure that the pre-reqs aren't in your Setup Capture, one thing you could also do was to install the software installation, and start the setup capture after the installation of the pre-reqs by the said software.

Tried it, but, [etc, etc]Clearly - to my mind, anyway - it hadn't completed at all. Are you sure you have 2.0 SP2? It might be that the (let's call it) master package and you disagree on what constitutes SP2.
Posted by: cygan 14 years ago
Fifth Degree Brown Belt
0
I assume you are using wise package studio ( I have not used wise for nearly a year now because I am using installshield)

how did you setup your setupcapture configuration

ie exclution list, capture deleted files / regkeys capture hardware etc


READ THIS INFO ON WISE


go to page 170

your setupcapture dialogs displays items that will be added to the installation ie green

<> means that item has changed or is updated by the installation

those files and keys that you have are displayed with <> in the dialog
if that is the case then that means they have just changed thats all

can they be deleted "YES"
Posted by: robor 14 years ago
Senior Yellow Belt
0
Are you certain that your setup is not installing dot.net as part of its setup routine
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