If you are going the "simple" route (just one PatchFamily per MSI) then never declare any children of the PatchFamily element. When that element is "empty", everything is included in that one solitary PatchFamily, and nothing is ignored (just don't ever rename that PatchFamily in any future patch, nor add any new PatchFamilies in the future unless their content is purely new stuff added by that patch. That would also require you to identify every fragment in your current patch family that wasn't added to the new one so that the two families don't overlap at all).
Putting any children in that element at all means you intend to support more complicated servicing scenarios AND you are in strict control over all the fragments that go into your authoring (that you ever care to service), including the ones that come from extensions. -----Original Message----- From: Schmitz, John [mailto:jschm...@mediacy.com] Sent: Friday, November 20, 2009 7:40 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Question about ComponentRef in PatchFamily I'm still trying to track down the PYRO0252 error from Pyro. I think it may be due to the ComponentRef element(s) in the PatchFamily element of the WSX source file. All the samples are very, very simple with just one component. My setup has many, many components. I found in the documentation of PatchFamily that I could use FeatureRef, which seemed to be the answer. I tried it, setting each FeatureRef's Id attribute to one of the names of the 3 features in the setup. However, that did not change the "transform" error at all. I couldn't really tell if that was proper usage from the documentation of FeatureRef, which seems to be more oriented towards using it in the source for a new setup, rather than a patch for pyro. Can someone show me an example of using FeatureRef elements to refer to the features in a setup, which would get pyro to look up all the components of those features? Otherwise, I'm afraid that I'm going to have to write a patch WSX that lists each and every one of those many, many components. Any help, suggestions or samples greatly appreciated. Thanks, John Media Cybernetics ############################################################################ ########## CONFIDENTIALITY NOTICE: This email transmission and its attachments contain confidential and proprietary information of Princeton Instruments, Acton Research, Media Cybernetics and their affiliates and is intended for the exclusive and confidential use of the intended recipient. Any use, dissemination, printing, or copying of this transmission and its attachment(s) is strictly prohibited. If you are not the intended recipient, please do not read, print, copy, distribute or take action in reliance upon this message. If you have received this in error, please notify the sender immediately by telephone or return email and promptly delete all copies of the original transmission and its attachments from your computer system. ############################################################################ ########### ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
