IIRC I had similar issues when attempting to create patches using the Pyro method in WiX 3.0 hence I've stuck with the PatchWiz method. I'm sure if I stuck at it I could probably work out what's going wrong when I try using the Pyro method but since I have a method which works there's not much incentive.
Travis have you tried using the PatchWiz method? It's described in the WiX.chm (you'll require the Windows SDK installed to get the required tools which is freely downloadable from microsoft.com). You may find it works more reliably than the Pyro method for your situation. Palbinder Sandher Software Deployment & IT Administrator T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Tony Juricic [mailto:tjuri...@tradestation.com] Sent: 18 September 2010 22:57 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How does patching decide which files to includein msp? It may be a problem with a 'new' WiX patching, as opposed to WiX patching that is just a wrapper around the legacy PatchWiz.dll. I think I encountered similar issues in the past and decided to stick with PatchWiz.dll for the time being. Except for bugs in Windows XP versions (and these seem to be patch application, or MSPatcha.dll versions for XP, bugs) my experience is that PatchWiz.dll processes small binary differences well enough to be useful. -----Original Message----- From: Travis Gaff [mailto:tra...@pc-doctor.com] Sent: Friday, September 17, 2010 7:49 PM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does patching decide which files to include in msp? Thanks for the reply. Just to be clear this is not an install time issue in which certain files are not updated because their modification times have changed. I am able to extract the .msp file immediately after creation and confirm that files are not included that I wish to include. Applying the patch in Orca shows the same issues. It looks like this is occurring at the patch assembly level. -----Original Message----- From: Tony Juricic [mailto:tjuri...@tradestation.com] Sent: Friday, September 17, 2010 3:28 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] How does patching decide which files to include in msp? These are not WiX rules but MSI rules and are documented on MSDN site, somewhere in install patching section. -----Original Message----- From: Travis Gaff [mailto:tra...@pc-doctor.com] Sent: Thursday, September 16, 2010 12:48 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How does patching decide which files to include in msp? Hello WiX users, I am trying to construct a .msp file to patch a several hundred file installation. However I am finding that a large number of files are not ending up in the final .msp file. Right now I suspect many of these are due to both the new and the old version of the file having the same version number; we're fixing this. However I have some files that do not have a version number and do have an internal change but are not in the msp. They appear to have little difference from most of the other files, they're all added with individual components to a .wxs by our build system. How does WiX decide which files to include in a patch using the pyro/torch method? By comparing several files I suspect it does the following: 1) if a file has a version number, check it, if same version skip file 2) if file doesn't have version number but there is a size difference: patch it? (I haven't verified this) 3) if no version number AND file is same size: diff the file or use creation date? What rules does WiX use to determine which files should be included in the msp? Background: All components are in 2 features. The 2nd feature is a sub-feature of the first and right now I am not even looking at its 2 shortcuts. The *patch.wxs file includes: <ComponentRef Id='co_mainui.exe' /> (a component of the main feature) <PropertyRef Id='ProductVersion'/> (to update the ARP program version) The patch is generated using .wixpdb files with torch and pyro: candle patch.wxs -dcodepage=1252 -ext WiXUtilExtension -dtop_projects_dir=C:\projects light -o out.wixmsp -cultures:en-us -ext WixUIExtension patch.wixobj -ext WiXNetFxExtension -ext WiXUtilExtension -dtop_projects_dir=C:\projects torch -t patch -p -pedantic -xi build1.wixpdb build2.wixpdb -out out.mst pyro out.wixmsp -out out.msp -t patch out1.mst I am using 3.5.1916.0, however I had similar issues in 3.0. Thank you for any help you can offer. Travis Gaff, Software Engineer PC-Doctor, Inc. 9805 Double R Boulevard, Suite 301 Reno, NV 89521 CONFIDENTIALITY The information contained in this message is confidential. It is intended to be read only by the individual or entity to whom it is addressed or by an authorized designee. If the reader of this message is not the intended recipient, be aware that distribution of this message in any form is strictly prohibited. If you have received this message in error, please immediately notify the sender and destroy any copy of this message. TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ------------------------------------------------------------------------ -- ---- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ------------------------------------------------------------------------ ------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
