Just to clarify:
If you implement this pattern (BTW: heat uses this pattern by default):
<Fragment>
<ComponentGroup Id="CompSet13">
<ComponentRef Id="Comp1"/>
<ComponentRef Id="Comp2"/>
<ComponentRef Id="Comp3"/>
</ComponentGroup>
</Fragment>
<Fragment>
<Component Id="Comp1">
...
</Component>
</Fragment>
<Fragment>
<Component Id="Comp2">
...
</Component>
</Fragment>
<Fragment>
<Component Id="Comp3">
...
</Component>
</Fragment>
And then in your patch you reference Comp2 you will only patch Comp2 (Comp1 and
Comp3 will be excluded from the patch).
If in your patch you reference CompSet13 then nothing will be patched (given
the current design).
If in your patch you don't reference anything then everything will be patched
(special case where we default to "everything").
As always, if something patched was not changed between the two versions, it
will not be included in the patch (doesn't matter if it was included or not).
-Blair Murri
> From: jocoo...@jackhenry.com
> To: wix-users@lists.sourceforge.net
> Date: Mon, 29 Jul 2013 18:41:19 +0000
> Subject: Re: [WiX-users] [Patch] Best practice using fragments
>
> It depends. It is often desired to localize changes to one assembly. Even
> if the versions of the other assemblies have changed, often the code content
> has not changed. This needs to be verified by regression testing and there
> is some risk.
>
> That being said, in general, I would prefer to patch all changed assemblies.
>
> --
> John Merryweather Cooper
> Build & Install Engineer - ESA
> Jack Henry & Associates, Inc.®
> Shawnee Mission, KS 66227
> Office: 913-341-3434 x791011
> jocoo...@jackhenry.com
> www.jackhenry.com
>
>
>
>
> -----Original Message-----
> From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
> Sent: Monday, July 29, 2013 1:17 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] [Patch] Best practice using fragments
>
> I think the part you are missing is " all changed components from that
> fragment will show up in your patch". I can't imagine only wanting a patch
> to contain a subset of changed components.
>
> -----Original Message-----
> From: Phill Hogland [mailto:phogl...@rimage.com]
> Sent: Monday, July 29, 2013 11:40 AM
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] [Patch] Best practice using fragments
>
> I am relatively new to WiX 3.7 and MSI (and having lots of fun with the great
> WiX documentation and information available in the forum). As I get my
> BA/msi functional I am trying to review best practices and I came across a
> post at:
> http://stackoverflow.com/questions/471424/wix-tricks-and-tips
>
> In particular:
> "Put Components which may be patched individually inside their own Fragments
>
> It goes for both making product installers and patches that if you include
> any component in a fragment, you must include all of the components in that
> fragment. In the case of building an installer, if you miss any component
> references, you'll get a linking error from light.exe. However, when you make
> a patch, if you include a single component reference in a fragment, then all
> changed components from that fragment will show up in your patch."
>
> I hope to always do Major Update builds. and the boss seems to agree.
> However the boss may change his mind and at some point expect me to create a
> patch. I have tried to implement the 'one resource per component' pattern
> with auto generated GUIDs, in logical ComponentGroups of related files. I
> have one ComponentGroup per Fragment. But if we did do a patch, I expect
> that they would only want to change one or two files and not include all of
> the files in a ComponentGroup. Now I am wondering if I need to go back and
> restructure my project to only have 'one component pre fragment' (and I guess
> this means not use ComponentGroups)?
>
> Other than the above post, I did not find this suggestion of creating one
> fragment per file discussed in any other forum or tutorial. I tried to
> follow the structure of the WiX 3.7 tools setup and that seems to be working
> as I test my project. I guess I am looking for advice on best practice to be
> ready to do a patch if I really have too someday down the road.
>
> Thanks;
> Phill
>
>
>
> --
> View this message in context:
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-Best-practice-using-fragments-tp7587660.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent caught
> up. So what steps can you take to put your SQL databases under version
> control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent caught
> up. So what steps can you take to put your SQL databases under version
> control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
> NOTICE: This electronic mail message and any files transmitted with it are
> intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or privileged
> information.
> Any unauthorized review, use, printing, saving, copying, disclosure or
> distribution
> is strictly prohibited. If you have received this message in error, please
> immediately advise the sender by reply email and delete all copies.
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
