hmmm I'm not thinking right now at all the appoaches what might get wrong
when both MSI + (MSI + Transform) run on the system. Only apout the
approach to modify an MSI by transform. In general it should be possible to
transform an MSI into another using a mst file. So I think of 2 approaches:
-
Torch for generating
transform + apply that transform...
This is where I had the problem. I created the two msi packages (a and
a.modified) and I created the transform (brand.mst). The difference between
the two MSI packages was that I used Orca to extract and then import a
changed Icon from
hmmm sorry just had a brief look in MSDN. msts seem to not to fulfill the
needs for file transformation (which are stored in embedded cabs):
A transform can modify information that is in any persistent table in
the installer
Thank you for pointing that link out. From reading the MSDN link I
understand why what I tried to do did not work. Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/torch-create-transform-tp7594463p7594633.html
Sent from the wix-users
As far as I know, a transform file is a file used during the patch-making
process, but can't be used directly to perform a transform. It needs to be
joined with a patch file. The patch file has the knowledge of what the
transform applies to. Without it, I don't think Windows would know what to
do
5 matches
Mail list logo
