Im not very well versed in torch and pyro so I will just post what I do to make simple msps. Perhaps having a second sample will enable you to spot the differences and commonalities. The patch is created from a pair of admin installations. This is the first hotfix for a released product.
Patch.wxs: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Patch ..> <Media Id="5000" Cabinet="Product.cab"> <!-- Id must be higher than any sequence number in the original File table. Cabinet must match the original cabinet file name. --> <PatchBaseline Id="RTM" /> <!-- Id created for the patches baseline. --> </Media> <PatchFamilyRef Id="StudioPatchFamily" /> <!-- References the patch family(s) required from the fragment below that are included in this patch. --> </Patch> <Fragment> <!-- Id created for this patch family. It can be grown (only) in later patches. The Version is the Version of the patch family and is used to sequence patches within the family. It should be incremented in later patches. --> <PatchFamily Id='StudioPatchFamily' Version='1.0.0.0' Supersede='no'> <ComponentRef Id="Sdl.LanguagePlatform.TranslationMemoryTools.Comp.8AA78051_FA80_44FF_BB4A_00E10662D40E" /> <!-- Component from the original MSI to replace. --> </PatchFamily> </Fragment> </Wix> Command lines: "%WIXPATH%\torch.exe" -nologo -t patch -xo -ax "%ROOT%\Binaries" -p "%ROOT%\Base\%MSIName%" "%ROOT%\Target\%MSIName%" -out "%ROOT%\Work\Diff.Wixmst" "%WIXPATH%\candle.exe" -nologo "%ROOT%\Patch.wxs" -out "%ROOT%\Work\Patch.wixobj" "%WIXPATH%\light.exe" -nologo "%ROOT%\Work\Patch.wixobj" -out "%ROOT%\Work\Patch.WixMsp" "%WIXPATH%\pyro.exe" -nologo "%ROOT%\Work\Patch.WixMsp" -out "%ROOT%\%PatchName%" -t RTM "%ROOT%\Work\Diff.wixmst" -----Original Message----- From: Schmitz, John [mailto:jschm...@mediacy.com] Sent: 23 November 2009 14:41 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with building patch Yes, that's one thing that I have held constant. I think that my problem troubleshooting this is that this error has multiple possible causes, at least two as indicated by the error message quoted below. Is it possible for a future version to break these very different causes into several more distinct error codes? Error message: "Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade." Also contributing to my difficulty troubleshooting is the fact that the "transform" itself is completely opaque to me. Maybe it's my ignorance of WIX and/or Windows Installer itself, but between the torch and pyro steps I don't know how to see what WIX "thinks" is going on. After having tried literally every possible combination of naming of the PatchBaseline Id, the Cabinet, the PatchFamily Id and even the files themselves, I am convinced that my error is somehow due to the second suggested cause. My later follow-on message with the subject "Question about ComponentRef in PatchFamily" is my attempt to somehow make progress with this, working on the ASSUMPTION that the transform I am giving pyro is in fact empty. Thanks, John -----Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, November 23, 2009 4:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with building patch Is the PatchBaseLine Id in the .wxs the same as the -t argument in pyro ? It needs to be. -----Original Message----- From: Schmitz, John [mailto:jschm...@mediacy.com] Sent: 20 November 2009 19:11 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Help with building patch Since several of you have suggested trying the torch/pyro method of creating a patch, I am trying that. Sorry to be a pain, but I'm stuck on the pyro step. Gabor's tutuorial uses the word "Sample" in a LOT of places and no matter what I try in my actual example, I get a PYRO0252 error. The text of the error message doesn't give me a lot of clues as to what I'm doing wrong. Specifically, I have no idea exactly what "transform" it is looking for. None of the other tools up to that point report any error, but then I can see that pyro is the one that ties it all together. Any help or clues or pointers to other tutorials that use more descriptive names would be EXTREMELY appreciated. I'm already two weeks late getting this patch out! Thanks, John ________________________________________ From: Schmitz, John Sent: Friday, November 20, 2009 11:57 AM To: Schmitz, John Subject: RE: [WiX-users] Help with building patch I found Gábor DEÁK JAHN's tutorial, and I'm trying to figure out how to apply the pyro/torch method to my setups, which involve multiple .WSX and .WIXOBJ files. Thanks, John Media Cybernetics ________________________________________ From: Schmitz, John Sent: Friday, November 20, 2009 10:54 AM To: General discussion for Windows Installer XML toolset. Subject: RE: [WiX-users] Help with building patch Sounds interesting, but I don't understand how I would do that from the help page. It talks about two text files - are those supposed to represent the hundreds of files in my installation? Can you point me towards any sort of tutorial using pyro, etc., because as I stated earlier, I have no idea what they do. My apologies on that point, but I got WIX as part of a setup/installer building software, and their emphasis is on using their software, which effectively hides all the use of WIX under the hood. This might be exactly what I need to fix my problems, because right now, my application does not work when I install the original release and patch it to the .0.1 version with the patch, while it works perfectly if I install the full .0.1 setup that I have to build as the "reference" for the MSIMSP build process. Thanks, John Media Cybernetics ________________________________________ From: Blair [os...@live.com] Sent: Friday, November 20, 2009 3:23 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] Help with building patch We had a build process that ran from a service account in a "build lab" of over a thousand machines. We discovered that msimsp.exe/patchwiz.dll will sometimes pop up a dialog box if we didn't do a good enough job catching all the possible error conditions and stall waiting for its OK button to be pressed, which was an absolute disaster in our build environment. Pyro/torch/et al proved to be a savior for us to be able to build MSPs as a routine development activity instead of only 3-4 times per public release at the most. Further, if you suppress ICE validation (since ICE validation requires either an interactive login or administrative privileges) you can use wixpdb files and build MSP files without having to grant your build process any admin privilege (makes network admins happier). You can't do that with admin installs that will eventually require administrator's privs to install. -----Original Message----- From: Schmitz, John [mailto:jschm...@mediacy.com] Sent: Monday, November 16, 2009 8:33 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with building patch The way I understand a previous comment from Blair, there was no intention to deprecate the 2.0 approach to patches. Unless I am misunderstanding something, the 2.0 approach is much, much more useful for an automated build than the 3.0 approach. ________________________________________ From: Pally Sandher [pally.sand...@iesve.com] Sent: Monday, November 16, 2009 10:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with building patch Rob he's trying to use v2.0 how-to guide with the v3.5 toolset. I'd wait for someone else to verify this is an actual bug as it works completely fine in v3.0. 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: Rob Mensching [mailto:r...@robmensching.com] Sent: 16 November 2009 15:32 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Help with building patch Yes, please open a bug on v3.5. That is under development and bugs help us quickly find what was recently broken. On Mon, Nov 16, 2009 at 7:12 AM, Schmitz, John <jschm...@mediacy.com> wrote: > I installed and switched to using WIX 2.0 (stable). This clarified two > things: > > 1) SOME of the changes that I specify in my bug are indeed only needed > to adapt the WSX file to version 3.5. The original code in the page > works with 2.0 IF you know to save it as a WSX file and use it as the > source for the compilation. > > 2) 3.5 does NOT work and 2.0 DOES work. Should I enter a bug on 3.5? > > Thanks, > John > ________________________________________ > From: Schmitz, John > Sent: Sunday, November 15, 2009 8:36 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Help with building patch > > I'm using 3.5. > > Message Sent with NotifySync > > -----Original Message----- > > From: os...@live.com > Sent: Sat, 14 Nov 2009 19:33:06 America/New_York > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] Help with building patch > > > Version 3.0 supports both the version 2 method (msimsp.exe/PatchWiz) > and the "pure WiX" method (torch/pyro). Version 3.5 retains that > support. > > Each of those two methods in the version 3 docs are described on two > different pages. > > Not sure on the error message (although I haven't looked at the code yet). > The TargetImages probably refers to the table itself, but with a path > to the MSI file itself in the error message as being the missing > symbol seems like something isn't quite right. Which version/build of > the toolset are you actually using? > > -----Original Message----- > From: Schmitz, John [mailto:jschm...@mediacy.com] > Sent: Saturday, November 14, 2009 1:20 PM > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] Help with building patch > > Hi, > > I have worked my way through understanding most of the things left out > of or incorrect in the "Patch Building" page of Authoring (at > http://wix.sourceforge.net/manual-wix2/patch_building.htm). (I've > entered a bug on the page with what I've found along the way.) > > I just noticed that this is a version 2 page, and the version 3 page > takes a totally different and (for me useless) approach. So I don't > actually know if what I'm trying to do is possible in 3.5 or not. > > I'm down to just one error, which only cropped up after modifying the > WSX code to use the TargetImage attribute of the PatchSequence. Here's > the > error: > > > Patch.wsx(39) : error LGHT0094 : Unresolved reference to symbol > 'TargetImages:<full path to my target MSI file>'' in section > 'PatchCreation:{C42BF9ED-EDDA-46C0-97E3-BE0EC2D0750E}'. > > > I've doubled checked the actual path I'm using in place of <full path > to my target MSI file>, and it is definitely the correct path to the > file - copying it from the error message and pasting it onto the end of "dir" > command in a command prompt results in a directory listing of the file. > > There's a difference between "TargetImages" (plural) in the error > message, and the "TargetImage" attributed that is used, but I'm > assuming that's just a typo in the error message itself. > > Can anyone explain how to troubleshoot this? > > 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 > > > ---------------------------------------------------------------------- > -------- 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 > > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------ ------ 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 ---------------------------------------------------------------------------- -- 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 ------------------------------------------------------------------------------ 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 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. ------------------------------------------------------------------------------ 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 ------------------------------------------------------------------------------ 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
