Admin images are MSIs that do not contain embedded cabs where the files are laid-out in "source-directory" layout using their 8.3 filenames according to the File table's FileName column, which is what you get when you perform an "administrative installation" of an MSI.
The "path" part of the -ax <path> option is the "path" part of the -x <path> option, which is the place that torch copies the files it extracts from both the administrative install and the binary (and other) table(s) that are then used by pyro.exe to generate the correct inputs into the Patch table. That path normally should normally NOT be the path to the admin install location. -----Original Message----- From: nearnick [mailto:n...@nearglobal.com] Sent: Monday, October 26, 2009 2:58 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Merge Modules and Patching Hi guys, I'm still having trouble using torch with the admin images and cannot find much instructions for it. Could you clear up a couple of basic questions for me? What are Admin images - these are the "msi"s? I notice some examples around where 2 of these are fed into the torch commandline after "-t patch". When I try this it is asking me for paths to source files within my installer but in competely the wrong place (like the directory where the installer is, not where the source files are). I am also unsure of what to put for the "-ax" path option. This is the path to the admin images so the same directory I have the "msi"s? Why would it need this, when i am feeding the path to two msi files later on? I am still fundamentally trying to solve the problem of patching over changing merge modules. I made the merge modules also, so could theoretically do away with them and just add everything into the msi to start with but am hoping to be able to overcome the case where i already have deployed with the merge and need to patch up. Any more help and advice appreciated, you've already helped me a long way! Svet Bonev wrote: > > WiX 3.0 patches produced using torch on wixpdbs will not include payload > coming from merge modules. This is by design because the merge modules are > merged *after* the wixpdbs are created. > > You have 2 options: > 1) Use admin images instead of wixpdbs. > 2) Change your build process to use melt.exe on the merge modules to > decompile them to native WiX and then change your authoring to use > ComponentGroupRef instead of Merge/MergeRef. > > Using admin images is most likely the cheaper path you can take. > > -----Original Message----- > From: Pally Sandher [mailto:pally.sand...@iesve.com] > Sent: Monday, October 05, 2009 3:52 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Merge Modules and Patching > > Are you totally sure the patch doesn't contain the new files from the > merge module? Have you checked a verbose log of applying the patch? You > may find the problem is Windows Installer not patching the files rather > than them not being included in the patch. If you have files with > resources (executables, DLL's, OCX's etc) and you haven't incremented the > version numbers, Windows Installer won't patch the file as it looks at the > version numbers, sees them as being the same & assumes they are the same > even if the files themselves are completely different (obviously this only > happens for files with resources, for 'normal' > files it will compare timestamps and/or file sizes). > > I've not used the "WiX only" method of generating patches as I started > using the Windows SDK method when I was using WiX 2.0 & I'm happy enough > with it not to want to change it so some, all or none of this may or may > not be applicable here. > > > 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: nearnick [mailto:n...@nearglobal.com] > Sent: 05 October 2009 09:53 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Merge Modules and Patching > > > So i guess I'll just have to extract the merge module and add its > contents to the installer package. That way I know the patch will > definetly pick up any changes. > Thanks anyway. > > > nearnick wrote: >> >> They'd be wixpdbs. >> >> >> Blair-2 wrote: >>> >>> Which files are the inputs to torch (admin-installed MSIs, wixpdbs, >>> or wixouts)? >>> >>> -----Original Message----- >>> From: nearnick [mailto:n...@nearglobal.com] >>> Sent: Wednesday, September 30, 2009 9:12 AM >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] Merge Modules and Patching >>> >>> >>> Hi I have this probably quite simple problem with my patching system >>> due to merge modules, but cannot find an answer anywhere. Between two > >>> versions of my wix installer the merge module containing a load of >>> dlls has changed. >>> Both versions of the installer work, however the patch I created to >>> go from one to the other does not and it is because the patch has not > >>> included the new merge module. >>> I am simply using the Merge component for which the source ('src'), >>> attribute has changed and obviously the cointents of the source merge > >>> module are now different. >>> Why would the torch tool not pick up the difference and update >>> accordingly? >>> Any help / advice would be much appreciated >>> -- >>> View this message in context: >>> http://n2.nabble.com/Merge-Modules-and-Patching-tp3743641p3743641.htm >>> l Sent from the wix-users mailing list archive at Nabble.com. >>> >>> --------------------------------------------------------------------- >>> ------- >>> -- >>> Come build with us! The BlackBerry® Developer Conference in SF, >>> CA is the only developer event you need to attend this year. >>> Jumpstart your developing skills, take BlackBerry mobile applications > >>> to market and stay ahead of the curve. Join us from November >>> 9-12, 2009. Register now! http://p.sf.net/sfu/devconf >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> --------------------------------------------------------------------- >>> --------- Come build with us! The BlackBerry® Developer >>> Conference in SF, CA is the only developer event you need to attend >>> this year. Jumpstart your developing skills, take BlackBerry mobile >>> applications to market and stay ahead of the curve. Join us from >>> November 9-12, 2009. Register now! >>> http://p.sf.net/sfu/devconf >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >> >> > > -- > View this message in context: > http://n2.nabble.com/Merge-Modules-and-Patching-tp3743641p3767673.html > Sent from the wix-users mailing list archive at Nabble.com. > > ------------------------------------------------------------------------ > ------ > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and > stay ahead of the curve. Join us from November 9-12, 2009. Register > now! http://p.sf.net/sfu/devconf > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ---------------------------------------------------------------------------- -- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ---------------------------------------------------------------------------- -- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register > now! > http://p.sf.net/sfu/devconf > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/Merge-Modules-and-Patching-tp3743641p3891049.html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
