component.
In my case, the file that I want to be a companion file (the one that is not
getting patched) is key path file.
So I cannot make it a companion file, correct?
-Original Message-
From: Kajal Kumar Biswas [mailto:kbis...@adobe.com]
Sent: Monday, October 15, 2012 5:42 AM
To: General
patch and it is not patching the file. So we are
trying to see how we can now fix the problem (so that the msp updates the file
correctly) caused by the released mst.
Thanks
Uma-
-Original Message-
From: Kajal Kumar Biswas [mailto:kbis...@adobe.com]
Sent: Sunday, October 14, 2012 10:33 PM
When the mst is applied, the msi cache is not updated with the file version at
the end of the installation and hence during patching the file is not updated.
What you can do this try creating the mst correctly, such that it does not
update the file version in the file table.
Can you let me know
I was trying to create a localized setup in Wix. Lets say I support 20
languages.
So, objective is to produce all the 20 mst's.
Using InstallShield in one build I can create the msi and the and all the 20
transform files.
Now I want to achieve this process using WIX.
What I have figured out so f
components and propertyrefs for properties. Just add
into your family.
-Original Message-----
From: Kajal Kumar Biswas [mailto:kbis...@adobe.com]
Sent: 03 October 2012 14:32
To: wix-users@lists.sourceforge.net
Cc: Akshat Kumar Jain
Subject: [WiX-users] Creating patch for minor upgrade
Hi,
I&#x
Hi,
I'm creating a patch using the wix toolset (not using the pcp technique).
I can create the patch successfully and can orca the msi and view the contents
of the patch.
But the problem is the ProductVersion does not get bumpted up while I open the
patch over the target msi in orca.
Steps follo
6 matches
Mail list logo
