Is there any fault in recapturing a MSI ??
0 Comments   [ + ] Show Comments

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.

Answers

0
Yes. Don't. Use a transform if you need to effect changes to an MSI.
Answered 06/06/2008 by: VBScab
Red Belt

Please log in to comment
0
Is it strictly ..dont ..or with some precautions , we can if we are in a unavoidable situation!
Answered 06/06/2008 by: dpu_bansal83
Orange Belt

Please log in to comment
0
Well, that's what I generally say: Do NOT unless it's unavoidable. However, I have yet to encounter a situation where I've had to re-package an MSI. Others have, I know - and people I respect, too, so those situations do arise - but even when provoked to the limit, I have managed to avoid it.
Answered 06/06/2008 by: VBScab
Red Belt

Please log in to comment
0
As Ian said; it's not recommended, special for vendor MSIs.
If you do capture and MSI you will not be able to use future updates/patches provided by that vendor if you do not reproduce the exact feature/component (& recourse) details.
In most cases it will be enuf to modify your needs through a transform but just have in mind that depending on what you add to the transform it's not certain you will be able to use the future vendor MSI/MSP/MSM either.

I've been in some situations where I had to recapture the MSI.
It can be a bit hard to find out what some custom actions performs from the vendor MSI which you maybe have to reproduce depending on what they do of course.

If you must do this make sure to enter that into the documentation for the package.
Make sure there is no advertise (Darwin Descriptor) info in the newly produced MSI.
Answered 06/06/2008 by: AngelD
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity