The last time I built an MSP file, I had only one PatchFamily and it had NO
children at all. I built it this way:
<Wix>
<Patch>
<PatchFamily Id="NeutralPatchFamily"
Version="$(env._BLDVERMAJOR).$(env._BLDVERMINOR).$(env._BLDNUMMAJOR).$(env._
BLDNUMMINOR)" Supersede="yes"/>
</Patch>
</Wix>
To have the PatchFamily in a different fragment from the Patch element (as
you have) you would need to include an appropriate PatchFamilyRef to pull in
the corresponding fragment.
However, to use your authoring for your patch (where you list everything you
are patching), you would need to change your dialog authoring like this
(adding the ID to your UI element):
<Wix>
<Product>
...
<UI Id='ProgressDlg'>
<Dialog Id='ProgressDlg' />
...
</UI>
</Product>
...
<Wix>
-----Original Message-----
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com]
Sent: Monday, January 04, 2010 3:39 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] How to patch an installer dialog using WIX 3.0?
Blair, if we don't have ANY references under PatchFamily, how can we tell
WIX which change should be included in the patch? Without listing every
changed component/property/etc. in the patch WXS file, none of the changes
are making to the final MSP.
FYI, I am able to patch custom actions, components, etc. using their
corresponding Ref elements under PatchFamily element. However, when a new
dialog is added to the updated MSI, I see this change in all the transform
files, but the final MSP does not have this change.
Below is an excerpt from my patch's WXS file. Note that the component,
custom action and the property are patched as expected.
<Wix>
<Patch>
...
</Patch>
<Fragment>
<PatchFamily Id="NeutralPatchFamily"
Version="$(env._BLDVERMAJOR).$(env._BLDVERMINOR).$(env._BLDNUMMAJOR).$(env._
BLDNUMMINOR)" Supersede="yes">
<ComponentRef
Id="abcdef.XXXXXXXX_XXXX_XXXX_XXXX_XXXXXXXXXXXX"/>
<CustomActionRef Id="_Set_ProgressType1" />
<PropertyRef Id="ProgressType0" />
<UIRef Id="ProgressDlg" />
</PatchFamily>
</Fragment>
</Wix>
And this is how the dialog is defined in the MSI's WXS file.
<Wix>
<Product>
...
<UI>
<Dialog Id='ProgressDlg' />
...
</UI>
</Product>
...
<Wix>
Thanks,
Sharat Janapareddy
~ 40269
-----Original Message-----
From: Blair [mailto:os...@live.com]
Sent: Monday, January 04, 2010 2:24 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] How to patch an installer dialog using WIX 3.0?
Most patches should not have any references under PatchFamily (nor more than
one PatchFamily). That will cause ALL changes between the target and
upgraded images to be included in the patch.
Some (generally very large and complicated) setups require scoping the
changes into groups/series/buckets where different changes are tracked
separately. PatchFamilies were implemented for them.
-----Original Message-----
From: Sharat Janapareddy [mailto:sharat.janapare...@microsoft.com]
Sent: Monday, January 04, 2010 1:58 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] How to patch an installer dialog using WIX 3.0?
What do we need to include in a patch WXS file to let WIX know that the
patch should include a new dialog that is added to the installer UI? I tried
this with UIRef element under PatchFamily, with the ID of the dialog, but it
does not seem to include it in the patch.
Thanks,
Sharat Janapareddy
~ 40269
----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community Take
advantage of Verizon's best-in-class app development support A streamlined,
14 day to market process makes app distribution fast and easy Join now and
get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
----------------------------------------------------------------------------
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
