... I was thinking of the following:
http://msdn.microsoft.com/en-us/library/aa370890(VS.85).aspx
AllowProductCodeMismatches
Set to '1' for True if the
ProductCode<http://msdn.microsoft.com/en-us/library/aa370854(VS.85).aspx>
Property may differ between the upgraded images listed in the UpgradedImages
Table<http://msdn.microsoft.com/en-us/library/aa372378(VS.85).aspx> and the
target images listed in the TargetImages Table. Set to '0' or blank to mean
False if the product codes must be the same.
AllowProductVersionMajorMismatches
Set to '1' to mean True if the first field (the major version field) of the
ProductVersion<http://msdn.microsoft.com/en-us/library/aa370859(VS.85).aspx>
Property may differ between upgraded images and target images. Set to '0' or
blank to mean False if the major versions must match.
... which appear to be more related to the PatchCreation element...
From: John Nannenga [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 5:15 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Multiple instance patches
I'm not one 100% positive here, but I think some of the validations had to do
with the generation of the patch based on two images, not the patch application
itself (in the old school way of genning a patch with MSIMSP from PCP files).
If the two images used in patch transform generation didn't have the same
product code and the ProductID validation was set to no, then you would not get
an error. Otherwise, an error would be returned during patch generation
letting you know that your inputs might not be valid, etc...
[ If I'm wrong or that sounds ludicrous, I'm going to blame it on hitting the
eggnog too hard this holiday season... :) ]
From: Matt Ziegler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 09, 2008 4:32 PM
To: Windows Installer XML toolset developer mailing list
Subject: Re: [WiX-devs] Multiple instance patches
It does look like the pyro code doesn't add in the semi-colon separated string
for target product codes, the code is there to create the string but the list
used to create the string doesn't get updated with information from the
wixinstancetransforms table. If I make sure that pyro creates the correct
string the patch will work. Attached is the change that should populate all of
the product codes, forgive me if this addition is in the wrong location,
haven't had time to dive completely into the source.
I would have assumed that ignoring the ProductId in the Validate element would
have worked as well but either WiX doesn't set this property correctly or the
windows installer doesn't like it.
Matt
On Mon, Dec 8, 2008 at 12:05 PM, Peter Marcu <[EMAIL PROTECTED]<mailto:[EMAIL
PROTECTED]>> wrote:
I believe we likely missed adding the instances to the TargetProductCode when
we we added support for instances. However, based on the Patch authoring I see
below, you are ignoring the ProductId in the patch using the Validate element.
This should prevent msi from doing that check when it tries to apply to the
patch. Heath, any ideas?
<PatchBaseline Id="RTM">
<Validate ProductId="no" UpgradeCode="no" ProductVersion="Major"
ProductVersionOperator="GreaterOrEqual"/>
</PatchBaseline>
<snip />
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
WiX-devs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-devs
