Did you rebuild any of the files when you created the second MSI ? If so, then they will be different and will potentially be pulled into the patch.
I assume you mean file sequence numbers, rather than component. Its normal for patched files to get new file sequence numbers. -----Original Message----- From: Muzikayise Flynn Buthelezi [mailto:muzkay...@gmail.com] Sent: 05 October 2012 10:26 To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] patching issue: adding new file works but this throws out old files Sequence numbers in msi Good Morning Team, trust everyone is well today. We have a complex installer made up of many wxs files, and we are now investigating wix patching. As an example Product.wxs OtherA.wxs OtherB.wxs FeatureY.wxs. We want to add a new component to OtherA.wxs. So we do that like this and add the component ref to the existing component group <Component Id="SampleComponent2" Guid="{0487C0F6-DE1F-443C-8D75-1F38FD098E4F}" DiskId="1"> <File Id="ANewfiletxt" Name="A New file.txt" Source="A New file.txt" /> </Component We run the commands candle, light and torch. Then update the patch.wxs to include the new componentref created above and create the patch using candle, light and pyro. The issue is that the patch is 50Mb or higher, and secondly when opening up the Original .msi in orca and viewing the patch the component sequence numbers for some files are being changed. So the questions are 1. Why is the patch so large? it should only be about 1MB since we only added 1 file 2. Are the component sequence numbers being changed because we are adding a new component in the middle (ie. in OtherA.wxs)? Should new components be added to a new feature to avoid this? 3. Is there logging or a method of determining why certain files are being included in the patch when running pyro, as we don't expect such a large patch. this is confusing because when we do the same test on a simple test project we get the desired results but when we apply this to main complex project we get this weird behavior. thanks, -- Best always, Muzi 082 594 4807 Light, Love & Prosperity in Abundance!!! ----------------------------------------------------------------------------- - Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
