I figured it out. Deep down in the comments on one of Peter Marcu's Blog posts about patching:
"The PatchFamily filters on components and the fragments they are contained within. E.g. if you reference a component that [is] contained within a fragment with 10 other components. The patch will contain all 11 components." - John Hopefully someone else will find this information helpful. -And -----Original Message----- From: Andy Glass [mailto:agl...@laserfiche.com] Sent: Wednesday, March 10, 2010 3:30 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patching a single component It looks like that would work for patching using .pcp files, since when you do the required administrative install, you have control over which files are actually present. I was hoping for a solution in which I could still use the .wixpdb files to generate a .wixmst. -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Wednesday, March 10, 2010 3:15 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Patching a single component I'm not sure where this is specified in WiX patching, but the PCP file has a TargetImages table with an IgnoreMissingSrcFiles option that sounds like what you want: http://msdn.microsoft.com/en-us/library/aa372066(VS.85).aspx Phil Wilson -----Original Message----- From: Andy Glass [mailto:agl...@laserfiche.com] Sent: Wednesday, March 10, 2010 1:46 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] Patching a single component As part of my first foray into the world of patching, I have been tasked with creating hotfix patches for our product. As part of the daily build, the version numbers for all files in the product are incremented, but I only want to patch the specific files that were fixed as part of the hotfix. After reading through the tutorial, various blogs, and the mailing list archives, I got the implication that adding a ComponentRef as a child of my PatchFamily would do what I want, so I went ahead and created a patch for Component A. After installing the patch, not only was the file in Component A updated to the new version, so were all other files that had changed between the builds. Is there some way to create a patch that only includes a single file, despite the two .wixpdb files used to create it having many other differences, or would I need to generate the patch using a .wixpdb file that only contained the change for the file I wish to patch? -Andy ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at Portland House, Bressenden Place, London, SW1E 5BF (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
