Are you saying that there is some way to get better error diagnostics from Torch? I added -v option for verbosity but it has no effect.
In fact, I can't even figure out how do validation flags validate?! For example, once I run Torch with -val y, next time with -val v, keeping the same wixout input files. I would expect some validation error to be reported: I mean, update versions of my DLLs can't be both larger and smaller than the target versions! However Torch reports no issues in either case, just silently outputs wixmst file which, according to Pyro, contains 120 MB of nothing. I certainly have-p option which is essential according to Peter's blog. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 11:04 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Does Pyro (or Torch) ignore 4-th version number? There is a share proderrors or something Pete Yates Senior Systems Developer DDC - Distributed & Components Team HBOS I&I IT B/1/C/243 (7725) 34383 / (0117) 376 4383 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Juricic Sent: 31 July 2008 15:56 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Does Pyro (or Torch) ignore 4-th version number? I have 120 MB large Wixmst created by Torch and when I pass it to Pyro it comes back with the message PYRO1079 saying that patch cabinet contains no files. My DLLs in RTM and Update respectively differ in the last, 4-th version number, plus the binaries themselves are different. Using SDK tools for patch creation these DLLs would be updated when applying the patch. I tested that long before I started using WiX and I am 100% sure that SDK doesn't ignore fourth version number for file substitution rules. So I am wondering if Pyro is ignoring binary differences if first 3 version numbers are the same? Patch.wxs content is the following: <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Patch AllowRemoval="yes" Classification="Update" Codepage="1252" ... various other attributes> <Media Id="1000" Cabinet="RTM.cab" EmbedCab="yes"> <PatchBaseline Id="RTM"/> </Media> <PatchFamily Id="MyPatchFamily" Version="1.0.0" Supersede="yes"> <ComponentRef Id="some component" /> ... a bunch of components follows </PatchFamily> </Patch> </Wix> Thanks ------------------------------------------------------------------------ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users . ------------------------------------------------------------------------ ---------------------------------------------- HBOS plc, Registered in Scotland No. SC218813. Registered Office: The Mound, Edinburgh EH1 1YZ. HBOS plc is a holding company, subsidiaries of which are authorised and regulated by the Financial Services Authority. HBOS is a carbon neutral company. Help keep it that way. Please don't print this message unless you really must. ======================================================================== ====== ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
