Re: [WiX-users] Assistance with creating a patch
On 02-Aug-12 13:09, Hoover, Jacob wrote: >The one benefit I saw from the AdminInstall/PatchCreation method is I > could free up disk space by only storing the MSI's and when building the > patch use a batch file to extract all the MSI's, create the patch, and then > purge (at the cost of IO and time). You can get the same benefits using Melt and WiX patching, avoiding all the limitations of MsiMsp. -- sig://boB http://joyofsetup.com/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Assistance with creating a patch
There are no bugs currently open on torch/pyro so there are no planned updates. Please open bugs and be as specific as possible about the issue. Patching issues can be particularly difficult to reproduce if complete detail is not provided. On Thu, Aug 2, 2012 at 11:40 AM, Jeanne Dixon wrote: > Going back to the old patch creation method worked! > > I followed the example in the link but I had to make a few changes (some > of the properties were old). > > Here is my new wxs patch file: > > http://schemas.microsoft.com/wix/2006/wi";> > Id="d0723206-7815-4e2e-9bee-c338de83696f" > CleanWorkingFolder="yes" > OutputPath="ADS_Patch1.pcp" > WholeFilesOnly="yes"> > > Description="Patch Test for ADS" > Comments="Patch Test for ADS" > Manufacturer="my company"/> > > AllowRemoval="yes" > Description="Patch Test for ADS" > ManufacturerName="my company" > TargetProductName="Automated Data Systems 7" > MoreInfoURL="http://www.mywebsite.com/"; > Classification="Update" > DisplayName="Patch Test for ADS" /> > > MediaSrcProp="ADS_Patch1" > Name="ADSPatch" > SequenceStart="5000"> > SourceFile="C:\ADS_AutoUpdate\ads_install_patch1\admin\ads_install.msi" > Id="ADS_Patch1"> > SourceFile="C:\ADS_AutoUpdate\ads_install\admin\ads_install.msi" Order="2" > Id="ADS_Install" IgnoreMissingFiles="no" /> > > > > Sequence="1.0.1.0" > Supersede="yes" /> > > > > > And here are the commands I ended up using to get it to work. > > "C:\program files\wix toolset v3.6\bin\candle.exe" ADSPatch1.wxs > "C:\program files\wix toolset v3.6\bin\light.exe" ADSPatch1.wixobj -out > ADSPatch1.pcp > " c:\program files\microsoft sdks\windows\v6.0a\bin\msimsp" -s > ADSPatch1.pcp -p ADSPatch1.msp -l patch.log > > I am not sure what is supposed to go into the MediaSrcProp, so I just put > something in. Also, I don't know what the Sequence under PatchSequence is > supposed to be so I made it the version number of the patch update. I > guess I can look at the patch through Orca to see if it looks ok. It worked > so for now I am happy. > > > Does anyone know if there are planned updates/bug fixes to correct > torch/pyro to work like the old way (or to just work the way it is > advertised)? > > -Original Message- > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > Sent: Thursday, August 02, 2012 1:09 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Assistance with creating a patch > > I could never get the new patch building mechanism ( > http://wix.sourceforge.net/manual-wix3/wix_patching.htm) to work, so I > fell back to the older patch creation method. ( > http://wix.sourceforge.net/manual-wix3/patch_building.htm) For what it's > worth, the wixpdb files are XML files. From what I remember, the > expectation was that your wixpdb's would also have a matching private build > source folder to reference the files. As such, if you are using 2 admin > install images but are still using the "new" method, then it really isn't > looking at the admin install. > > The one benefit I saw from the AdminInstall/PatchCreation method is I > could free up disk space by only storing the MSI's and when building the > patch use a batch file to extract all the MSI's, create the patch, and then > purge (at the cost of IO and time). > > If you are going to try the old way, please post the fragments and > commands you are using. > > -Original Message- > From: Jeanne Dixon [mailto:jdi...@cots.com] > Sent: Thursday, August 02, 2012 10:18 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Assistance with creating a patch > > This is getting really frustrating... > > I followed the instructions to make an administrative install for both the > original and updated versions. I reran torch (using the msi files instead > of wixpdb) and pyro built the patch without errors. However, the patch is > still not including the changed files (I used Orca to verify the files were > not being applied). > > I also got advic
Re: [WiX-users] Assistance with creating a patch
Going back to the old patch creation method worked! I followed the example in the link but I had to make a few changes (some of the properties were old). Here is my new wxs patch file: http://schemas.microsoft.com/wix/2006/wi";> http://www.mywebsite.com/"; Classification="Update" DisplayName="Patch Test for ADS" /> And here are the commands I ended up using to get it to work. "C:\program files\wix toolset v3.6\bin\candle.exe" ADSPatch1.wxs "C:\program files\wix toolset v3.6\bin\light.exe" ADSPatch1.wixobj -out ADSPatch1.pcp " c:\program files\microsoft sdks\windows\v6.0a\bin\msimsp" -s ADSPatch1.pcp -p ADSPatch1.msp -l patch.log I am not sure what is supposed to go into the MediaSrcProp, so I just put something in. Also, I don't know what the Sequence under PatchSequence is supposed to be so I made it the version number of the patch update. I guess I can look at the patch through Orca to see if it looks ok. It worked so for now I am happy. Does anyone know if there are planned updates/bug fixes to correct torch/pyro to work like the old way (or to just work the way it is advertised)? -Original Message- From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] Sent: Thursday, August 02, 2012 1:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I could never get the new patch building mechanism (http://wix.sourceforge.net/manual-wix3/wix_patching.htm) to work, so I fell back to the older patch creation method. (http://wix.sourceforge.net/manual-wix3/patch_building.htm) For what it's worth, the wixpdb files are XML files. From what I remember, the expectation was that your wixpdb's would also have a matching private build source folder to reference the files. As such, if you are using 2 admin install images but are still using the "new" method, then it really isn't looking at the admin install. The one benefit I saw from the AdminInstall/PatchCreation method is I could free up disk space by only storing the MSI's and when building the patch use a batch file to extract all the MSI's, create the patch, and then purge (at the cost of IO and time). If you are going to try the old way, please post the fragments and commands you are using. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Thursday, August 02, 2012 10:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch This is getting really frustrating... I followed the instructions to make an administrative install for both the original and updated versions. I reran torch (using the msi files instead of wixpdb) and pyro built the patch without errors. However, the patch is still not including the changed files (I used Orca to verify the files were not being applied). I also got advice from Peter: "If it helps, these are our command lines for wixpdb patching. "C:\Program Files (x86)\WiX Toolset v3.6\bin\torch.exe" -v -p -xi old\SetupProject2.wixpdb new\SetupProject2.wixpdb -out patch\diff.wixmst "C:\Program Files (x86)\WiX Toolset v3.6\bin\candle.exe" patch.wxs "C:\Program Files (x86)\WiX Toolset v3.6\bin\light.exe" patch.wixobj -out patch\patch.wixmsp "C:\Program Files (x86)\WiX Toolset v3.6\bin\pyro.exe" patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst I'm having difficulty finding anything particularly wrong with your source files. Id remove AdminImage="yes" and add in into the family but I doubt those are the problem." Before trying the admin install I reviewed these comments and my command lines are identical, and I added the PropertyRef to the patch but it still did not work. I put the AdminImage in as an attempt to get an admin installation, but I have not removed that yet. So it seems no matter what I try I cannot get my changed files included. I know I am really missing something, but I still have no idea what it may be. -Original Message----- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, August 02, 2012 10:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch An administrative installation is created using your built MSI. It's a bit like extracting files from a zip. Msiexec /a TARGETDIR= This thread on admin install patching may help http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-o r-Patch-creating-using-Visual-Studio-2010-tp7578891p7578899.html http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-didn t-build-with-wix-using-wix-.aspx may be useful though
Re: [WiX-users] Assistance with creating a patch
I cannot suggest a solution for the patch problem you currently have, but I might be able to suggest an alternative. I was unable to use the pure WiX patching technique, as I was attempting to patch a file in a merge module. The WiX help describes two methods of patch generation, the first WiX only (using pyro and torch), the second using patch creation properties. I was successfully able to generate a patch using this method. Using an administrative install from the original, and one from the patch, you can then generate a patch with the following commands: candle -o %PATCH%.wixobj PatchCreation.wxs light -o %PATCH%.pcp %PATCH%.wixobj msimsp -s %PATCH%.pcp -p patch/%PATCH%.msp -l %PATCH%.log I was able to build the sample patch as outlined in the help, then extend/modify the patch creation file to suit. good luck, bill -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Assistance-with-creating-a-patch-tp7579419p7579692.html Sent from the wix-users mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Assistance with creating a patch
I could never get the new patch building mechanism (http://wix.sourceforge.net/manual-wix3/wix_patching.htm) to work, so I fell back to the older patch creation method. (http://wix.sourceforge.net/manual-wix3/patch_building.htm) For what it's worth, the wixpdb files are XML files. From what I remember, the expectation was that your wixpdb's would also have a matching private build source folder to reference the files. As such, if you are using 2 admin install images but are still using the "new" method, then it really isn't looking at the admin install. The one benefit I saw from the AdminInstall/PatchCreation method is I could free up disk space by only storing the MSI's and when building the patch use a batch file to extract all the MSI's, create the patch, and then purge (at the cost of IO and time). If you are going to try the old way, please post the fragments and commands you are using. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Thursday, August 02, 2012 10:18 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch This is getting really frustrating... I followed the instructions to make an administrative install for both the original and updated versions. I reran torch (using the msi files instead of wixpdb) and pyro built the patch without errors. However, the patch is still not including the changed files (I used Orca to verify the files were not being applied). I also got advice from Peter: "If it helps, these are our command lines for wixpdb patching. "C:\Program Files (x86)\WiX Toolset v3.6\bin\torch.exe" -v -p -xi old\SetupProject2.wixpdb new\SetupProject2.wixpdb -out patch\diff.wixmst "C:\Program Files (x86)\WiX Toolset v3.6\bin\candle.exe" patch.wxs "C:\Program Files (x86)\WiX Toolset v3.6\bin\light.exe" patch.wixobj -out patch\patch.wixmsp "C:\Program Files (x86)\WiX Toolset v3.6\bin\pyro.exe" patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst I'm having difficulty finding anything particularly wrong with your source files. Id remove AdminImage="yes" and add in into the family but I doubt those are the problem." Before trying the admin install I reviewed these comments and my command lines are identical, and I added the PropertyRef to the patch but it still did not work. I put the AdminImage in as an attempt to get an admin installation, but I have not removed that yet. So it seems no matter what I try I cannot get my changed files included. I know I am really missing something, but I still have no idea what it may be. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, August 02, 2012 10:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch An administrative installation is created using your built MSI. It's a bit like extracting files from a zip. Msiexec /a TARGETDIR= This thread on admin install patching may help http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-o r-Patch-creating-using-Visual-Studio-2010-tp7578891p7578899.html http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-didn t-build-with-wix-using-wix-.aspx may be useful though not exactly what you want. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 02 August 2012 14:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I have messed about with the patch some and while I got rid of the pyro error I still get a warning about the cab files being empty and the patch created basically contains nothing (when I look at it in Orca all I see is the version number has changed; no files are listed at all). I have been searching the web for more ideas how to fix this and it seems that maybe using the wixpdb files is not the way to go and I should be using the msi files for the transform. But these pages also say the build needs to be an "administrative installation". How do I do that? I have been using Visual Studio to create my msi files. Is there an option somewhere I am not setting to make them admin? I have tried using the msi files I have now and I get the same results, so maybe I am missing the administrative installation part? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you'r
Re: [WiX-users] Assistance with creating a patch
This is getting really frustrating... I followed the instructions to make an administrative install for both the original and updated versions. I reran torch (using the msi files instead of wixpdb) and pyro built the patch without errors. However, the patch is still not including the changed files (I used Orca to verify the files were not being applied). I also got advice from Peter: "If it helps, these are our command lines for wixpdb patching. "C:\Program Files (x86)\WiX Toolset v3.6\bin\torch.exe" -v -p -xi old\SetupProject2.wixpdb new\SetupProject2.wixpdb -out patch\diff.wixmst "C:\Program Files (x86)\WiX Toolset v3.6\bin\candle.exe" patch.wxs "C:\Program Files (x86)\WiX Toolset v3.6\bin\light.exe" patch.wixobj -out patch\patch.wixmsp "C:\Program Files (x86)\WiX Toolset v3.6\bin\pyro.exe" patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst I'm having difficulty finding anything particularly wrong with your source files. Id remove AdminImage="yes" and add in into the family but I doubt those are the problem." Before trying the admin install I reviewed these comments and my command lines are identical, and I added the PropertyRef to the patch but it still did not work. I put the AdminImage in as an attempt to get an admin installation, but I have not removed that yet. So it seems no matter what I try I cannot get my changed files included. I know I am really missing something, but I still have no idea what it may be. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Thursday, August 02, 2012 10:31 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch An administrative installation is created using your built MSI. It's a bit like extracting files from a zip. Msiexec /a TARGETDIR= This thread on admin install patching may help http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-o r-Patch-creating-using-Visual-Studio-2010-tp7578891p7578899.html http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-didn t-build-with-wix-using-wix-.aspx may be useful though not exactly what you want. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 02 August 2012 14:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I have messed about with the patch some and while I got rid of the pyro error I still get a warning about the cab files being empty and the patch created basically contains nothing (when I look at it in Orca all I see is the version number has changed; no files are listed at all). I have been searching the web for more ideas how to fix this and it seems that maybe using the wixpdb files is not the way to go and I should be using the msi files for the transform. But these pages also say the build needs to be an "administrative installation". How do I do that? I have been using Visual Studio to create my msi files. Is there an option somewhere I am not setting to make them admin? I have tried using the msi files I have now and I get the same results, so maybe I am missing the administrative installation part? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch
Re: [WiX-users] Assistance with creating a patch
An administrative installation is created using your built MSI. It's a bit like extracting files from a zip. Msiexec /a TARGETDIR= This thread on admin install patching may help http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Minor-upgrade-o r-Patch-creating-using-Visual-Studio-2010-tp7578891p7578899.html http://blogs.msdn.com/b/pmarcu/archive/2008/05/30/patching-something-you-didn t-build-with-wix-using-wix-.aspx may be useful though not exactly what you want. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 02 August 2012 14:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I have messed about with the patch some and while I got rid of the pyro error I still get a warning about the cab files being empty and the patch created basically contains nothing (when I look at it in Orca all I see is the version number has changed; no files are listed at all). I have been searching the web for more ideas how to fix this and it seems that maybe using the wixpdb files is not the way to go and I should be using the msi files for the transform. But these pages also say the build needs to be an "administrative installation". How do I do that? I have been using Visual Studio to create my msi files. Is there an option somewhere I am not setting to make them admin? I have tried using the msi files I have now and I get the same results, so maybe I am missing the administrative installation part? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:ps
Re: [WiX-users] Assistance with creating a patch
I have messed about with the patch some and while I got rid of the pyro error I still get a warning about the cab files being empty and the patch created basically contains nothing (when I look at it in Orca all I see is the version number has changed; no files are listed at all). I have been searching the web for more ideas how to fix this and it seems that maybe using the wixpdb files is not the way to go and I should be using the msi files for the transform. But these pages also say the build needs to be an "administrative installation". How do I do that? I have been using Visual Studio to create my msi files. Is there an option somewhere I am not setting to make them admin? I have tried using the msi files I have now and I get the same results, so maybe I am missing the administrative installation part? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table e
Re: [WiX-users] Assistance with creating a patch
I have tried that and it did not help. PDF files do not have version numbers. -Original Message- From: maksim.vazhe...@emc.com [mailto:maksim.vazhe...@emc.com] Sent: Thursday, August 02, 2012 5:27 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Assistance with creating a patch You should change version of the file which is included in the patch. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Wednesday, August 01, 2012 7:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Thank you for the link. I changed the upgrade install to the same name as the original install and the upgrade worked fine. However, this did not solve my initial problem - torch/pyro is not finding a difference so pyro is not building the patch. Any other ideas as to how I fix this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the
Re: [WiX-users] Assistance with creating a patch
You should change version of the file which is included in the patch. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Wednesday, August 01, 2012 7:45 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Thank you for the link. I changed the upgrade install to the same name as the original install and the upgrade worked fine. However, this did not solve my initial problem - torch/pyro is not finding a difference so pyro is not building the patch. Any other ideas as to how I fix this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they
Re: [WiX-users] Assistance with creating a patch
Thank you for the link. I changed the upgrade install to the same name as the original install and the upgrade worked fine. However, this did not solve my initial problem - torch/pyro is not finding a difference so pyro is not building the patch. Any other ideas as to how I fix this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 10:53 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows In
Re: [WiX-users] Assistance with creating a patch
You can't change the name of the MSI in a minor/small update. See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/MajorMinorSm all.htm is only used for major upgrades and won't affect what you're doing currently. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 15:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all f
Re: [WiX-users] Assistance with creating a patch
I don't know if this is related to why no changes are detected, but I put in the tags and tried to run the msi file as a minor upgrade through the msiexec command line. When I do that it starts to run the install (as opposed to giving me the message that a different version already exists), but then I get a message that it can't find the old install in the patch directory (C:\ads_udpate\install_patch1\bin\debug\ads_install.msi not found). My patch should be named ads_install_patch1.msi, which it is in the debug directory. I must be missing something somewhere that it is expecting the old file name instead of the new file name. Any idea where that would be? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 9:57 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all files in a directory called ads_install under the main directory for the first build, then changed the one file, then created a copy of the install directory and called it ads_patch1. This way all the files are only in one main directory and the only differences are the new install directory for the patch and the one file that has changed. Do I need to create an entire second main directory just for a patch? I would think the msi should contain
Re: [WiX-users] Assistance with creating a patch
It sounds like you've done it right so far. A patch IS a minor upgrade. A patch just a different way of packaging the upgrade. By leaving unchanged resources out, you can't do a first time install with it but it's smaller. The version number can be different in any field to be different in a minor or major update. What makes a minor update differ from a major update is the change in product code and hence the way Windows Installer runs it. Id forget about the 4th field of the product version entirely unless you really must have it. A file size change is a difference that torch and pyro will see, yes. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 14:31 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all files in a directory called ads_install under the main directory for the first build, then changed the one file, then created a copy of the install directory and called it ads_patch1. This way all the files are only in one main directory and the only differences are the new install directory for the patch and the one file that has changed. Do I need to create an entire second main directory just for a patch? I would think the msi should contain the changed file, and since the file size is different torch should be able to pick up the difference between them. What is the correct way to do this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 5:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I found your original message and it looks like you're updating a PDF. Those don't have Windows version resources, so ignore me there. You can remove those edits you made with Orca. The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match the -t argument passed to pyro, which you've given the value "RTM". Just change one of them so they have the same value. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 20:13 To: General discussi
Re: [WiX-users] Assistance with creating a patch
I built the first install with the old file, then changed the file and built the second install. Individually each install works fine, and the second install has the correct file with it. So I think the MSIs have been built properly. I also have changed the version number - in the first one it is 1.0.0.0 and in the second it is 1.0.1.0 (I changed the third number since it seems the last digit is ignored). I do see the pdf file name in the wixmst file. The files sizes are different but I am not sure if that qualifies for the binary diff between the 2 files (I would think it should). I will try changing the version number to be a minor upgrade, but doesn't that defeat the purpose of a patch? I have looked at both MSI files in Orca and I see the file sizes for the pdf file are different. As I have questioned before, is the file size change something that torch should see as a difference when building the wixmst file? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 8:56 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all files in a directory called ads_install under the main directory for the first build, then changed the one file, then created a copy of the install directory and called it ads_patch1. This way all the files are only in one main directory and the only differences are the new install directory for the patch and the one file that has changed. Do I need to create an entire second main directory just for a patch? I would think the msi should contain the changed file, and since the file size is different torch should be able to pick up the difference between them. What is the correct way to do this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 5:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I found your original message and it looks like you're updating a PDF. Those don't have Windows version resources, so ignore me there. You can remove those edits you made with Orca. The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match the -t argument passed to pyro, which you've given the value "RTM". Just change one of them so they have the same value. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 20:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I used Orca to put version numbers on the file in both msi projects and re-ran torch and pyro, but it still gives me the error about no valid transforms. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article
Re: [WiX-users] Assistance with creating a patch
How you build is up to you. As long as the MSIs that come out of the build contain the correct files, then it's a valid method. From your description, it's not clear if you're building the MSI before or after you change the file in the first ads_install directory, which might be where you're going wrong. You should validate that your MSIs have built properly and are correct by performing a minor upgrade using the 2 MSIs. If that fails, examine each one with Orca to check that the file table entries are what you expect. Look in the wixmst: you should be able to find your PDF file's name. If it's in the wixmst, then pyro will bring it into the patch if a binary diff of the 2 versions shows that they differ. You've only posted the wix source for the release version. Did you remember to change the product version (and retain the product code) in the second installer's source code ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 01 August 2012 12:11 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all files in a directory called ads_install under the main directory for the first build, then changed the one file, then created a copy of the install directory and called it ads_patch1. This way all the files are only in one main directory and the only differences are the new install directory for the patch and the one file that has changed. Do I need to create an entire second main directory just for a patch? I would think the msi should contain the changed file, and since the file size is different torch should be able to pick up the difference between them. What is the correct way to do this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 5:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I found your original message and it looks like you're updating a PDF. Those don't have Windows version resources, so ignore me there. You can remove those edits you made with Orca. The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match the -t argument passed to pyro, which you've given the value "RTM". Just change one of them so they have the same value. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 20:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I used Orca to put version numbers on the file in both msi projects and re-ran torch and pyro, but it still gives me the error about no valid transforms. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixo
Re: [WiX-users] Assistance with creating a patch
It is good to know I don't have to update all files with a version number. I redid my pyro statement to use "ADSPatch" but I still get the same error. I am obviously missing something. What I have tried to do is use the same directory for both builds. I have a directory (I'll refer to it as the main directory) that contains subordinate directories that contain all my source and support files . I put the wix build and all files in a directory called ads_install under the main directory for the first build, then changed the one file, then created a copy of the install directory and called it ads_patch1. This way all the files are only in one main directory and the only differences are the new install directory for the patch and the one file that has changed. Do I need to create an entire second main directory just for a patch? I would think the msi should contain the changed file, and since the file size is different torch should be able to pick up the difference between them. What is the correct way to do this? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, August 01, 2012 5:28 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I found your original message and it looks like you're updating a PDF. Those don't have Windows version resources, so ignore me there. You can remove those edits you made with Orca. The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match the -t argument passed to pyro, which you've given the value "RTM". Just change one of them so they have the same value. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 20:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I used Orca to put version numbers on the file in both msi projects and re-ran torch and pyro, but it still gives me the error about no valid transforms. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added ba
Re: [WiX-users] Assistance with creating a patch
I found your original message and it looks like you're updating a PDF. Those don't have Windows version resources, so ignore me there. You can remove those edits you made with Orca. The patchbaseline in the patch.wxs has the Id "ADSPatch". This Id must match the -t argument passed to pyro, which you've given the value "RTM". Just change one of them so they have the same value. -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 20:13 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I used Orca to put version numbers on the file in both msi projects and re-ran torch and pyro, but it still gives me the error about no valid transforms. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";>
Re: [WiX-users] Assistance with creating a patch
I used Orca to put version numbers on the file in both msi projects and re-ran torch and pyro, but it still gives me the error about no valid transforms. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it disp
Re: [WiX-users] Assistance with creating a patch
No, it does not. Does that mean I have to create a version for every file in my build? That's a lot of files! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, July 31, 2012 12:41 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it displays is a mix of the installation directory and
Re: [WiX-users] Assistance with creating a patch
Does your changed file have a version resource and, if so, did the version increase in the updated file ? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: 31 July 2012 17:28 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it displays is a mix of the installation directory and the destination folder from the installation. I have put AdminImage="yes" into both installation packages to made them admin so I can use the msi files in torch. This is my understanding of what I needed to do following the web pages I have read (which are many). I have tried using the admin version because I also read that if you use the wix
Re: [WiX-users] Assistance with creating a patch
I just read an article that made me realize I have an error in my pyro command. It should read: Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t ADSPatch ADSPatch1.wixmst This now gives me a warning: PYRO1079: the cab file does not contain any files. I do have the changed file in a ComponentRef in the patch file, so I am not sure why I got this. This is then followed by the error: PYRO0227: The transforms being built did not contain any references so it could not be created. So I am still at a stopping point where my transforms are not being built. I have looked at both msi files in Orca and the file sizes for the changed file are different. I though that was enough for it to see the differences but it does not seem that way. How do I get the processes to see the changed file? -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Tuesday, July 31, 2012 11:24 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it displays is a mix of the installation directory and the destination folder from the installation. I have put AdminImage="yes" into both installation packages to made them admin so I can use the msi files in torch. This is my understanding of what I needed to do following the web pages I have read (which are many). I have tried using the admin version because I also read that if you use the wixpdb files it does read the msi to find the file change and my updates are all currently within my working directory that I build the installation from, so the only file there is the latest one (so it will not be able to find the previous one). The msi files work fine for installation, but I
Re: [WiX-users] Assistance with creating a patch
Sorry for not getting back to this sooner. I am using visual studio to create the msi and wixpdb files for both versions. I then use light to create the patch .wixmsp file Light ADSPatch1.wixobj -out ADSPatch1.wixmsp Then I try to use pyro to build the patch Pyro ADSPatch1.wixmsp -out ADSPatch1.msp -t RTM ADSPatch1.wixmst The pyro command returns the error: PYRO0252: No valid transforms were provided. The torch error for some reason is now not coming up. I still don't understand why pyro does not see any valid transforms. -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Monday, July 16, 2012 1:01 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Assistance with creating a patch It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it displays is a mix of the installation directory and the destination folder from the installation. I have put AdminImage="yes" into both installation packages to made them admin so I can use the msi files in torch. This is my understanding of what I needed to do following the web pages I have read (which are many). I have tried using the admin version because I also read that if you use the wixpdb files it does read the msi to find the file change and my updates are all currently within my working directory that I build the installation from, so the only file there is the latest one (so it will not be able to find the previous one). The msi files work fine for installation, but I don't understand why I am getting the error below when I use them in torch. torch.exe : error TRCH0258 : The file 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' cannot be found. The part up to ADSD is where I am building my install (the source code is contained in a different directory) and the ADSD part is where I am telling the install to copy the exe file to after I specify the TARGETDIR directory in my wxs file. I have attached the product.wxs file and the patch wxs file. The file that I am trying to get built in as the patch is the "NoChart" file contained within the product.wxs file. I would prefer not to have multiple copies of the source code within each install directory, as that can get quite large. What am I doing wrong with this install and/or patch? Thanks in advance for the help! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's s
Re: [WiX-users] Assistance with creating a patch
It would be helpful to know the commands you are using to generate your initial packages as well as your patches. It sounds like you may be having a problem because the base path where its looking for the contents of your admin image doesn't exist. Does this location exist? 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' -Original Message- From: Jeanne Dixon [mailto:jdi...@cots.com] Sent: Friday, July 13, 2012 10:08 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] FW: Assistance with creating a patch I added back into the patch the componentref for the changed file and that got rid of the funny file error. However, I still have the No valid transforms error. It also seems mu file attachments did not go through, so I will paste them here. Product.wxs: http://schemas.microsoft.com/wix/2006/wi";> 1 Verifying Database Settings (DBUpdate=1) AND NOT (REMOVE="ALL") AND NOT (PATCH) Patch.wxs: http://schemas.microsoft.com/wix/2006/wi";> From: Jeanne Dixon [jdi...@cots.com] Sent: Friday, July 13, 2012 10:47 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] Assistance with creating a patch I am new to using WiX and have built my 2 installation packages successfully. The only difference between the first and second is an updated pdf file. I have tried to build the patch using torch with the .wixpdb files and I get a pryo error that says there are no valid transforms. If I try to use torch with the .msi files I get a strange error that says it can't find one of the files - the path it displays is a mix of the installation directory and the destination folder from the installation. I have put AdminImage="yes" into both installation packages to made them admin so I can use the msi files in torch. This is my understanding of what I needed to do following the web pages I have read (which are many). I have tried using the admin version because I also read that if you use the wixpdb files it does read the msi to find the file change and my updates are all currently within my working directory that I build the installation from, so the only file there is the latest one (so it will not be able to find the previous one). The msi files work fine for installation, but I don't understand why I am getting the error below when I use them in torch. torch.exe : error TRCH0258 : The file 'C:\ADS_AutoUpdate\ADS_Install\bin\debug\ADSD\ADS.exe' cannot be found. The part up to ADSD is where I am building my install (the source code is contained in a different directory) and the ADSD part is where I am telling the install to copy the exe file to after I specify the TARGETDIR directory in my wxs file. I have attached the product.wxs file and the patch wxs file. The file that I am trying to get built in as the patch is the "NoChart" file contained within the product.wxs file. I would prefer not to have multiple copies of the source code within each install directory, as that can get quite large. What am I doing wrong with this install and/or patch? Thanks in advance for the help! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@
