Hi all - I've been experimenting with torch/pyro/patching on our Wix installer,
which I'm proud to say has completely replaced InstallShield for our
application.
The thing I'm wondering about is this: do you have to use .wixpdb files as
input to torch, or can you use .msi's instead ? The docs imply the answer is
"yes". Everything works fine if I try using .wixpdb's but if I use .msi's I
get the following error from pyro :
"pyro.exe : error PYRO0315 : Source information is required for the product
'{GUID omitted}'. If you ran torch.exe with both target and updated .msi files,
you must first perform an administrative installation of both .msi files then
pass -a when running torch.exe."
Here's how I invoked torch :
"torch -p -xo orig\SetupProject1.msi new\SetupProject1.msi -out
patch\diff2.wixmst"
Are .wixpdb's really necessary to get this to work ? Do the .MSI's not contain
enough info by themselves ? Thanks for any info !
-Rob
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
