Installer XML toolset.
Subject: Re: [WiX-users] Instance transforms with the msi
Here's the key point from the SDK:
* To keep the nonfile data of each instance isolated, the base package
should collect nonfile data into sets of components for each instance. The
appropriate components should th
rmation location for
that instance changes. You'll need to change the component GUID in this
situation as well.
From: Michael Osmond [mosm...@baytech.com.au]
Sent: Monday, December 07, 2009 5:46 PM
To: General discussion for Windows Installer XML tools
Installer XML toolset.
Subject: Re: [WiX-users] Instance transforms with the msi
Each instance has a unique Product Code. Also, I was following the
guidelines from the Windows installer SDK (On how to author instance
transforms).
How do I install the same set of files for multiple instances using
indows Installer XML toolset."
To
"General discussion for Windows Installer XML toolset."
cc
Subject
Re: [WiX-users] Instance transforms with the msi
Each instance has a unique Product Code. Also, I was following the
guidelines from the Windows installer SDK (On how to autho
L toolset."
To
"General discussion for Windows Installer XML toolset."
cc
Subject
Re: [WiX-users] Instance transforms with the msi
Each instance has a unique Product Code. Also, I was following the
guidelines from the Windows installer SDK (On how to author instance
transform
XML toolset.
Subject: Re: [WiX-users] Instance transforms with the msi
Are you using the same component GUID for each of these keys? You can't
do that... It's breaking the component rules and all kinds of bad things
happen when you break the component rules.
Each distinct compone
Are you using the same component GUID for each of these keys? You can't
do that... It's breaking the component rules and all kinds of bad things
happen when you break the component rules.
Each distinct component keypath (the 'main' entry in a component) MUST
have a unique component GUID. Eac
7 matches
Mail list logo
