Re: [WiX-users] Patch with a simple file change
Bob Arnson-6 wrote: In addition to admin images, you can use Melt.exe to build an image you can use without -ax. I thought Melt only http://wix.sourceforge.net/manual-wix3/AllTools.htm dealt with merge modules (.msm). Special use, maybe? - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6975065.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
On 03-Nov-11 14:39, john.burak wrote: new). It would be nice if pyro just fetched them from the MSIs. In addition to admin images, you can use Melt.exe to build an image you can use without -ax. -- sig://boB http://joyofsetup.com/ -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
I browsed the bug database and eventually found out https://sourceforge.net/tracker/index.php?func=detailaid=2086871group_id=105970atid=642714 pyro actually diffs the files on disk and not from inside the MSIs. In other words, the 'before' and 'after' copy of files have to exist at the same time in different source directories. That's annoying because then I have to keep old copies of files (multiple gigs in large directory structure) in addition to the copies of these files are already in the previous MSIs. I think I have to make sure that the source paths for files point to the correct directory structures (old vs. new). It would be nice if pyro just fetched them from the MSIs. I think this will be a feature request. ;) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6960135.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
If you do an admin install from the source and target MSI's, you get the files. -- John Merryweather Cooper Jack Henry Associates, Inc. Build Install Engineer - jXchange Office: 913-341-3434 x791011 jocoo...@jackhenry.com -Original Message- From: john.burak [mailto:john.bu...@telvent.com] Sent: Thursday, November 03, 2011 1:39 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch with a simple file change I browsed the bug database and eventually found out https://sourceforge.net/tracker/index.php?func=detailaid=2086871group_id=105970atid=642714 pyro actually diffs the files on disk and not from inside the MSIs. In other words, the 'before' and 'after' copy of files have to exist at the same time in different source directories. That's annoying because then I have to keep old copies of files (multiple gigs in large directory structure) in addition to the copies of these files are already in the previous MSIs. I think I have to make sure that the source paths for files point to the correct directory structures (old vs. new). It would be nice if pyro just fetched them from the MSIs. I think this will be a feature request. ;) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6960135.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
I'll try to experiment with that sometime today. My assumption (from the bug-report comment) was that pyro or torch used the original source paths for the files, which won't be the same as the administrative install locations for my installers. This is all very strange to me. I feel like I must be misunderstanding something. :P - John John Cooper-2 wrote: If you do an admin install from the source and target MSI's, you get the files. -- John Merryweather Cooper Jack Henry Associates, Inc. Build Install Engineer - jXchange Office: 913-341-3434 x791011 JoCooper@ -Original Message- From: john.burak [mailto:john.burak@] Sent: Thursday, November 03, 2011 1:39 PM To: wix-users@.sourceforge Subject: Re: [WiX-users] Patch with a simple file change I browsed the bug database and eventually found out https://sourceforge.net/tracker/index.php?func=detailaid=2086871group_id=105970atid=642714 pyro actually diffs the files on disk and not from inside the MSIs. In other words, the 'before' and 'after' copy of files have to exist at the same time in different source directories. That's annoying because then I have to keep old copies of files (multiple gigs in large directory structure) in addition to the copies of these files are already in the previous MSIs. I think I have to make sure that the source paths for files point to the correct directory structures (old vs. new). It would be nice if pyro just fetched them from the MSIs. I think this will be a feature request. ;) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6960265.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
I think I figured it out! Using the pyro/torch approach, patching can be done from MSIs without the original source dirs. Sorry to add so much noise to the list. For the benefit of future generations, here is what I did that differed from the http://wix.sourceforge.net/manual-wix3/wix_patching.htm tutorial : - Administrative installs of both MSIs (put them in 1.0\admin and 1.1\admin) - Add the -ax direcotry flag to torch.exe. I pointed it to my patch directory: -ax patch\ (I don't know why this is necessary, but I get errors without it) - Remove -xi flag, add -xo flag to torch. - Point torch to 1.0\admin\product.msi (and 1.1\admin\product.msi) instead of the original 1.0\product.wixpdb (and 1.1\product.wixpdb). - John Burak john.burak wrote: I browsed the bug database and eventually found out https://sourceforge.net/tracker/index.php?func=detailaid=2086871group_id=105970atid=642714 pyro actually diffs the files on disk and not from inside the MSIs. In other words, the 'before' and 'after' copy of files have to exist at the same time in different source directories. That's annoying because then I have to keep old copies of files (multiple gigs in large directory structure) in addition to the copies of these files are already in the previous MSIs. I think I have to make sure that the source paths for files point to the correct directory structures (old vs. new). It would be nice if pyro just fetched them from the MSIs. I think this will be a feature request. ;) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6960657.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
That is essentially how I do it. I have a wixproj hacked to make my patch. In a PreBuildEvent, I have: if exist $(ProjectDir)Target\Admin\some.msi del /q $(ProjectDir)Target\Admin\some.msi if exist $(ProjectDir)Target\Admin\some-install-dir rmdir /s/q $(ProjectDir)Target\Admin\some-install-dir if exist $(ProjectDir)Upgrade\Admin\some.msi del /q $(ProjectDir)Upgrade\Admin\some.msi if exist $(ProjectDir)Upgrade\Admin\some-install-dir rmdir /s/q $(ProjectDir)Upgrade\Admin\some-install-dir In a PostBuildEvent, I have: copy /y $(TargetDir)en-us\$(TargetFileName) $(TargetDir)en-us\$(TargetName).wixmsp echo Be Patient while Admin Installs run . . . msiexec.exe /quiet /a $(ProjectDir)Target\some.msi INSTALLLEVEL=1000 TARGETDIR=$(ProjectDir)Target\admin echo Target Admin Install Complete msiexec.exe /quiet /a $(ProjectDir)Upgrade\some.msi INSTALLLEVEL=1000 TARGETDIR=$(ProjectDir)Upgrade\admin echo Upgrade Admin Install Complete $(WIX)bin\torch.exe -p -ax binaries -xo $(ProjectDir)Target\admin\some.msi $(ProjectDir)Upgrade\admin\some.msi -out $(TargetDir)diff.wixmst $(WIX)bin\pyro.exe $(TargetDir)en-us\$(TargetName).wixmsp -t GA $(TargetDir)diff.wixmst -out $(TargetDir)$(TargetName).msp some.msi is the name of the MSI's I'm patching against. And some-install-dir is the root folder of the admin install. It would be nice if the available patch projects supported using torch and pyro, but this works. -- John M. Cooper -Original Message- From: john.burak [mailto:john.bu...@telvent.com] Sent: Thursday, November 03, 2011 4:17 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Patch with a simple file change I think I figured it out! Using the pyro/torch approach, patching can be done from MSIs without the original source dirs. Sorry to add so much noise to the list. For the benefit of future generations, here is what I did that differed from the http://wix.sourceforge.net/manual-wix3/wix_patching.htm tutorial : - Administrative installs of both MSIs (put them in 1.0\admin and 1.1\admin) - Add the -ax direcotry flag to torch.exe. I pointed it to my patch directory: -ax patch\ (I don't know why this is necessary, but I get errors without it) - Remove -xi flag, add -xo flag to torch. - Point torch to 1.0\admin\product.msi (and 1.1\admin\product.msi) instead of the original 1.0\product.wixpdb (and 1.1\product.wixpdb). - John Burak john.burak wrote: I browsed the bug database and eventually found out https://sourceforge.net/tracker/index.php?func=detailaid=2086871grou p_id=105970atid=642714 pyro actually diffs the files on disk and not from inside the MSIs. In other words, the 'before' and 'after' copy of files have to exist at the same time in different source directories. That's annoying because then I have to keep old copies of files (multiple gigs in large directory structure) in addition to the copies of these files are already in the previous MSIs. I think I have to make sure that the source paths for files point to the correct directory structures (old vs. new). It would be nice if pyro just fetched them from the MSIs. I think this will be a feature request. ;) - John -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6960657.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Patch with a simple file change
[Sorry if you got this twice, I think I botched posting via Nabble the previous time] Hi, I tried the patching example given at http://wix.sourceforge.net/manual-wix3/wix_patching.htm but I changed it so the source-path points to a single file in both versions (1.0 vs 1.1), and I just change the file contents of the text file between building each installer. In other words, I compile the 1.0 installer, change the text file, compile the 1.1 installer, then make the MSP. This is more like what I'd be doing at work. The problem is, if I use the file contents given in the tutorial or anything similar (old: This is version 1.0, new: This is version 1.1) then it misses the file in the patch. It doesn't even include it in the CAB (I get an empty CAB warning). If I make the new value file drastically different (e.g. add a sentence or two more) then it detects the change and puts the file into the patch. Apparently this only happens using pyro/torch, and not when going the patchwiz rout. Anyone know, is this simply a known characteristic of the hashing algorithm used to detect changes? Is there a workaround to have it do a better comparison (perhaps an exact comparison)? I don't want a config file to be missed someday because it only differed slightly from the previous version. Thanks. - John Burak -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Patch-with-a-simple-file-change-tp6956231p6956231.html Sent from the wix-users mailing list archive at Nabble.com. -- RSA#174; Conference 2012 Save $700 by Nov 18 Register now#33; http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Patch with a simple file change
On 02-Nov-11 13:44, john.burak wrote: Anyone know, is this simply a known characteristic of the hashing algorithm used to detect changes? It's not a hash: If two files are the same length, the binder does a byte-by-byte comparison. If you can repro this with a simple case, please file a bug. -- sig://boB http://joyofsetup.com/ -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
