Vendor MSI Package + exe patch (converting an exe patcher to msp)
I'm wondering what strategies other people have used to deal with the scenario where a vendor releases a non windows installer based patch to a product that is originally provided in MSI format.
The approach I have used is to install the MSI, then spy the patch.exe installation. This is sub optimal, since it results in a seperate "patch msi" that must be removed independantly of the vendors MSI, and it doesn't preserve component codes. Ideally I'd like to capture the patch.exe to an MSP, so that it automatically removes files introduced with the patch when uninstalling the vendor MSI.
Some basic searches haven't turned up anything. Anyone done something similar?
The specific product I'm dealing with is Adobe Photoshop CS3, the updates are in proprietary format.
The approach I have used is to install the MSI, then spy the patch.exe installation. This is sub optimal, since it results in a seperate "patch msi" that must be removed independantly of the vendors MSI, and it doesn't preserve component codes. Ideally I'd like to capture the patch.exe to an MSP, so that it automatically removes files introduced with the patch when uninstalling the vendor MSI.
Some basic searches haven't turned up anything. Anyone done something similar?
The specific product I'm dealing with is Adobe Photoshop CS3, the updates are in proprietary format.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
India_Repackaging
15 years ago
Hi Andrew,
I am not aware of the fact whether the patch for Adobe Photoshop CS3 is not in windows installer format i.e. a msp file. However I guess that that most efficient way of handling this scenario would be to capture the patch.exe and create a patch i.e. a .msp file off it.
Then I sense one problem with this : that it is most likely that a transform would be created as Adobe Photoshop CS3 is a .msi file (I am guessing but if it is). Repairing the tranform would null the changes made by the patch. To be honest I have never worked on this but would be curious to know if anyone has faced any similar scenario that is given such a thing can happen. So to summarise can a transform and a patch co-exist for given .msi?
Sorry Andrew, if I am drifting from your post. [8|]
Cheers
I am not aware of the fact whether the patch for Adobe Photoshop CS3 is not in windows installer format i.e. a msp file. However I guess that that most efficient way of handling this scenario would be to capture the patch.exe and create a patch i.e. a .msp file off it.
Then I sense one problem with this : that it is most likely that a transform would be created as Adobe Photoshop CS3 is a .msi file (I am guessing but if it is). Repairing the tranform would null the changes made by the patch. To be honest I have never worked on this but would be curious to know if anyone has faced any similar scenario that is given such a thing can happen. So to summarise can a transform and a patch co-exist for given .msi?
Sorry Andrew, if I am drifting from your post. [8|]
Cheers
Posted by:
anonymous_9363
15 years ago
The specific product I'm dealing with is Adobe Photoshop CS3, the updates are in proprietary format.As a group, we need to storm Adobe's headquarters armed with heavy implements to begin an 'education' process, as these fools clearly have no idea how their products are used and deployed in the real world.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
