Re: [WiX-users] How does Torch decide which files changed?!
Hi, I'm having trouble with pyro, I get the PYRO0227 error even though I know there are changes between the files it's comparing. I even debugged the pyro c# code, what I saw was that the FileManager.CompareFiles works great, and the rows are marked RowOperation.Modify. but the GenerateTransform method that calls the MsiInterop.MsiDatabaseGenerateTransform returns the ERROR_NO_DATA(0xE8) means no differences were found I don't know why... When I go and change something manually in one of the text files I have everything works fine... but the .NET assemblies that is KNOW changed won't make it work... when it does work I get everything inside the msp files... Please help! Thanks. -Original Message- From: Blair [mailto:os...@live.com] Sent: יום ה 02 פברואר 2012 23:06 To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! I'm assuming that the attribute-less InstallExecute in this email is the line in the error message, correct? If so, then this really looks like a bug in dark.exe. The ?if? from the original source shouldn't have anything to do with the this bug in dark.exe. Go ahead and fix that line in the generated file after you file a bug against dark.exe. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, February 02, 2012 1:29 AM To: wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com; rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing I found out: (concerning the msi to wixpdb using dark, candle, light) I have another tag in my setup.wxs: ?if $(var.HasQsConfig) = true ? CustomAction Id=RunConfigInstall FileKey=QsConfig.exe ExeCommand= Execute=immediate Return=ignore / CustomAction Id=RunConfigUninstall FileKey=QsConfig.exe ExeCommand=RunMode=Uninstall Execute=immediate Return=ignore / InstallExecuteSequence Custom Action='RunConfigInstall' After='InstallFinalize' (NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL) /Custom Custom Action='RunConfigUninstall' After='CostFinalize' (Installed) /Custom /InstallExecuteSequence ?endif? Maybe it has something to do with the error since the generated wxs file (from the dark command) has this: InstallExecuteSequence Custom Action=RunConfigUninstall After=CostFinalize(Installed)/Custom Custom Action=RunConfigInstall After=InstallFinalize(NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL)/Custom InstallExecute / /InstallExecuteSequence Somehoe it generates an InstallExecute tag without the attribute... Thanks -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, February 01, 2012 6:55 PM To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! If the only changes in your bug fix are files in the file table, that should work. To rebuild your code you may consider using dark on your released MSI to get your base WIXPDB and to get your starting point for your bug fix. The REINSTALL property will be autoselected to be the smallest section of already installed features that cover all of the database changes contained in the patch if you don't override it (as you are proposing). Normally the default value should suffice, unless you have a complex feature/component tree or if you have files that don't lend themselves well to the file versioning rules. Your overridden value for REINSTALLMODE property will prevent application of registry and shortcuts from the patched view. If you don't have a requirement for the a flag, the default should suffice. Blair -Original Message- From: tome...@qualisystems.com mailto:tome...@qualisystems.com [mailto:tome...@qualisystems.com mailto:tome...@qualisystems.com ] Sent: Wednesday, February 01, 2012 12:26 AM To: wix-users@lists.sourceforge.net mailto:wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com mailto:alex...@qualisystems.com ; rone...@qualisystems.com mailto:rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and
[WiX-users] Pyro error: PYRO0227
Hi all, I'm having trouble with pyro, I get the PYRO0227 error even though I know there are changes between the files it's comparing. I even debugged the pyro c# code, what I saw was that the FileManager.CompareFiles works great, and the rows are marked RowOperation.Modify. but the GenerateTransform method that calls the MsiInterop.MsiDatabaseGenerateTransform returns the ERROR_NO_DATA(0xE8) means no differences were found I don't know why... When I go and change something manually in one of the text files I have everything works fine... but the .NET assemblies that is KNOW changed won't make it work... when it does work I get everything inside the msp files... Please help! Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Pyro error: PYRO0227
Hi all, I'm having trouble with pyro, I get the PYRO0227 error even though I know there are changes between the files it's comparing. I even debugged the pyro c# code, what I saw was that the FileManager.CompareFiles works great, and the rows are marked RowOperation.Modify. but the GenerateTransform method that calls the MsiInterop.MsiDatabaseGenerateTransform returns the ERROR_NO_DATA(0xE8) means no differences were found I don't know why... When I go and change something manually in one of the text files I have everything works fine... but the .NET assemblies that is KNOW changed won't make it work... when it does work I get everything inside the msp files... Please help! Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] install file from subfolder
Hi. I'm having problems with pyro. I get this error: (note the weird Patch.msp in the temp directory showing twice?!) Copyright (C) Microsoft Corporation. All rights reserved. Updating file information. Creating cabinet files. There will be '4' threads used to produce CAB files. Creating cabinet 'C:\Windows\TEMP\prkmnyfn\#RTM.cab'. Generating database. C:\Windows\TEMP\prkmnyfn\Patch.msp : error PYRO0103 : The system cannot find the file 'C:\Windows\TEMP\prkmnyfn\Patch.msp'. 2012-02-06 18:29:56,371 [3] ERROR ProductPatchBuilder - ExecuteCommand: Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2403.0 Copyright (C) Microsoft Corporation. All rights reserved. Updating file information. Creating cabinet files. There will be '4' threads used to produce CAB files. Creating cabinet 'C:\Windows\TEMP\prkmnyfn\#RTM.cab'. Generating database. C:\Windows\TEMP\prkmnyfn\Patch.msp : error PYRO0103 : The system cannot find the file 'C:\Windows\TEMP\prkmnyfn\Patch.msp'. The command I run is: pyro.exe Temp\Patch.wixmsp -out Temp\Patch.msp -t RTM Temp\diff.wixmst -v the diff.wixmst was create by torch, the 2 wixpdb files I used are EXACTLLY the same except for the wixFile table that has different paths to the newer and older files. (I find replace the path to reflect the location of the files since the MSI is generated in a directory I can't run the torch nor the pyro from). Thanks! -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How does Torch decide which files changed?!
As always, you are correct :) And yes, when I remove that line, or add an After/Before, it works great... Too bad, I was hoping on using dark to avoid having to save the PDB of each released version... I don't wanna hard code removal of this line in my script... Got any ideas? And Thanks again! -Original Message- From: Blair [mailto:os...@live.com] Sent: Thursday, February 02, 2012 11:06 PM To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! I'm assuming that the attribute-less InstallExecute in this email is the line in the error message, correct? If so, then this really looks like a bug in dark.exe. The ?if? from the original source shouldn't have anything to do with the this bug in dark.exe. Go ahead and fix that line in the generated file after you file a bug against dark.exe. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, February 02, 2012 1:29 AM To: wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com; rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing I found out: (concerning the msi to wixpdb using dark, candle, light) I have another tag in my setup.wxs: ?if $(var.HasQsConfig) = true ? CustomAction Id=RunConfigInstall FileKey=QsConfig.exe ExeCommand= Execute=immediate Return=ignore / CustomAction Id=RunConfigUninstall FileKey=QsConfig.exe ExeCommand=RunMode=Uninstall Execute=immediate Return=ignore / InstallExecuteSequence Custom Action='RunConfigInstall' After='InstallFinalize' (NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL) /Custom Custom Action='RunConfigUninstall' After='CostFinalize' (Installed) /Custom /InstallExecuteSequence ?endif? Maybe it has something to do with the error since the generated wxs file (from the dark command) has this: InstallExecuteSequence Custom Action=RunConfigUninstall After=CostFinalize(Installed)/Custom Custom Action=RunConfigInstall After=InstallFinalize(NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL)/Custom InstallExecute / /InstallExecuteSequence Somehoe it generates an InstallExecute tag without the attribute... Thanks -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, February 01, 2012 6:55 PM To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! If the only changes in your bug fix are files in the file table, that should work. To rebuild your code you may consider using dark on your released MSI to get your base WIXPDB and to get your starting point for your bug fix. The REINSTALL property will be autoselected to be the smallest section of already installed features that cover all of the database changes contained in the patch if you don't override it (as you are proposing). Normally the default value should suffice, unless you have a complex feature/component tree or if you have files that don't lend themselves well to the file versioning rules. Your overridden value for REINSTALLMODE property will prevent application of registry and shortcuts from the patched view. If you don't have a requirement for the a flag, the default should suffice. Blair -Original Message- From: tome...@qualisystems.com mailto:tome...@qualisystems.com [mailto:tome...@qualisystems.com mailto:tome...@qualisystems.com ] Sent: Wednesday, February 01, 2012 12:26 AM To: wix-users@lists.sourceforge.net mailto:wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com mailto:alex...@qualisystems.com ; rone...@qualisystems.com mailto:rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and rebuild my code and create the MSIs again MAKING SURE to use the same files.wxs created by the previous HEAT harvest (so the GUIDS will be the same). Now I have both wixpdb files without the change and with the change. I torch them to get the diff.wixmst. (using the -xi and -p flags) And then I pyro. (pyro.exe patch\patch.wixmsp -out patch.msp -t RTM patch\diff.wixmst -v) The customer needs to
Re: [WiX-users] How does Torch decide which files changed?!
Hi, Good to know about Dark.exe, didn't notice it till now :) I'm having problems after converting my Original MSI to WXS file, I try to Candle it so I can then light it to get the wixpdb, but I get this error: \\sqlsrv\tsinstallers\TestShell Suite\4.6.255 SP1\Data\Driver Builder\TestShell DriverBuilder Setup.wxs(2939) : error CNDL0072 : A InstallExecute element must have a Before attribute, After attribute, or a Sequence attribute. If I look at my original setup.wxs file the InstallExecute tag looks like this: InstallExecuteSequence InstallExecute After=RemoveExistingProducts/ /InstallExecuteSequence It does have an After attribute... what am I doing wrong... maybe it's the UNC path? Naa. -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, February 01, 2012 6:55 PM To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! If the only changes in your bug fix are files in the file table, that should work. To rebuild your code you may consider using dark on your released MSI to get your base WIXPDB and to get your starting point for your bug fix. The REINSTALL property will be autoselected to be the smallest section of already installed features that cover all of the database changes contained in the patch if you don't override it (as you are proposing). Normally the default value should suffice, unless you have a complex feature/component tree or if you have files that don't lend themselves well to the file versioning rules. Your overridden value for REINSTALLMODE property will prevent application of registry and shortcuts from the patched view. If you don't have a requirement for the a flag, the default should suffice. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Wednesday, February 01, 2012 12:26 AM To: wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com; rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and rebuild my code and create the MSIs again MAKING SURE to use the same files.wxs created by the previous HEAT harvest (so the GUIDS will be the same). Now I have both wixpdb files without the change and with the change. I torch them to get the diff.wixmst. (using the -xi and -p flags) And then I pyro. (pyro.exe patch\patch.wixmsp -out patch.msp -t RTM patch\diff.wixmst -v) The customer needs to install the msp with this command: MSIEXEC /update \\tomer-c-d3\Share\patch.msp REINSTALL=ALL REINSTALLMODE=a It seems a bit cumbersome, will it work? :) Thanks again. -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, January 30, 2012 9:51 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! One way to see what the transforms in a patch actually contain WRT any particular MSI, open the MSI in Orca, then open the MSP file using the Transform menu item View a patch. It will highlight the database changes, and in the case of files, you can look at the two file-related tables to see which files it thinks have been changed. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Saturday, January 28, 2012 10:59 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing, I opened the msp file with z7, there are only: exe dll (.net assemblies) and one txt file!? there. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 27, 2012 10:24 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! Torch marks up the database changes. Including -p causes it to leave the unchanged portions of the database intact so they will be present for Pyro to use in its processing. It is Pyro that looks at the two files and determines if they are the same or not, and it promotes files that compare as different to be considered as changed and thus be included with the other marked database changes. If you use WIXOUT or WIXPDB files then fragment boundaries are considered in the comparisons, so if you specify references to things to include in your patch family/families, things
Re: [WiX-users] How does Torch decide which files changed?!
One more thing I found out: (concerning the msi to wixpdb using dark, candle, light) I have another tag in my setup.wxs: ?if $(var.HasQsConfig) = true ? CustomAction Id=RunConfigInstall FileKey=QsConfig.exe ExeCommand= Execute=immediate Return=ignore / CustomAction Id=RunConfigUninstall FileKey=QsConfig.exe ExeCommand=RunMode=Uninstall Execute=immediate Return=ignore / InstallExecuteSequence Custom Action='RunConfigInstall' After='InstallFinalize' (NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL) /Custom Custom Action='RunConfigUninstall' After='CostFinalize' (Installed) /Custom /InstallExecuteSequence ?endif? Maybe it has something to do with the error since the generated wxs file (from the dark command) has this: InstallExecuteSequence Custom Action=RunConfigUninstall After=CostFinalize(Installed)/Custom Custom Action=RunConfigInstall After=InstallFinalize(NOT Installed AND RUN_QSCONFIG = true) OR (REINSTALL)/Custom InstallExecute / /InstallExecuteSequence Somehoe it generates an InstallExecute tag without the attribute... Thanks -Original Message- From: Blair [mailto:os...@live.com] Sent: Wednesday, February 01, 2012 6:55 PM To: 'General discussion for Windows Installer XML toolset.' Cc: Alex Abugov; Ronen Akri Subject: Re: [WiX-users] How does Torch decide which files changed?! If the only changes in your bug fix are files in the file table, that should work. To rebuild your code you may consider using dark on your released MSI to get your base WIXPDB and to get your starting point for your bug fix. The REINSTALL property will be autoselected to be the smallest section of already installed features that cover all of the database changes contained in the patch if you don't override it (as you are proposing). Normally the default value should suffice, unless you have a complex feature/component tree or if you have files that don't lend themselves well to the file versioning rules. Your overridden value for REINSTALLMODE property will prevent application of registry and shortcuts from the patched view. If you don't have a requirement for the a flag, the default should suffice. Blair -Original Message- From: tome...@qualisystems.com mailto:tome...@qualisystems.com [mailto:tome...@qualisystems.com mailto:tome...@qualisystems.com ] Sent: Wednesday, February 01, 2012 12:26 AM To: wix-users@lists.sourceforge.net mailto:wix-users@lists.sourceforge.net Cc: alex...@qualisystems.com mailto:alex...@qualisystems.com ; rone...@qualisystems.com mailto:rone...@qualisystems.com Subject: Re: [WiX-users] How does Torch decide which files changed?! Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and rebuild my code and create the MSIs again MAKING SURE to use the same files.wxs created by the previous HEAT harvest (so the GUIDS will be the same). Now I have both wixpdb files without the change and with the change. I torch them to get the diff.wixmst. (using the -xi and -p flags) And then I pyro. (pyro.exe patch\patch.wixmsp -out patch.msp -t RTM patch\diff.wixmst -v) The customer needs to install the msp with this command: MSIEXEC /update \\tomer-c-d3\Share\patch.msp file:///\\tomer-c-d3\Share\patch.msp REINSTALL=ALL REINSTALLMODE=a It seems a bit cumbersome, will it work? :) Thanks again. -Original Message- From: Blair [mailto:os...@live.com mailto:os...@live.com ] Sent: Monday, January 30, 2012 9:51 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! One way to see what the transforms in a patch actually contain WRT any particular MSI, open the MSI in Orca, then open the MSP file using the Transform menu item View a patch. It will highlight the database changes, and in the case of files, you can look at the two file-related tables to see which files it thinks have been changed. -Original Message- From: tome...@qualisystems.com mailto:tome...@qualisystems.com [mailto:tome...@qualisystems.com mailto:tome...@qualisystems.com ] Sent: Saturday, January 28, 2012 10:59 PM To: wix-users@lists.sourceforge.net mailto:wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing, I opened the msp file with z7,
Re: [WiX-users] How does Torch decide which files changed?!
Hi, After all your help :) I think I have a solution to my problem, please let me know what you think: My product is already installed on customers machines, I didn't save the wixpdb nor the files.wxs (the Heat harvest file) of those releases, since I didn't know I'll need them to issue a patch, I also don't have the product Id since it's * (auto generated). So, I need to rebuild my code and create the MSIs again with the same code as the released product making sure I hard code the Original Product Id I take from the released MSI. Then I make my changes (fix the bug or whatever) and rebuild my code and create the MSIs again MAKING SURE to use the same files.wxs created by the previous HEAT harvest (so the GUIDS will be the same). Now I have both wixpdb files without the change and with the change. I torch them to get the diff.wixmst. (using the -xi and -p flags) And then I pyro. (pyro.exe patch\patch.wixmsp -out patch.msp -t RTM patch\diff.wixmst -v) The customer needs to install the msp with this command: MSIEXEC /update \\tomer-c-d3\Share\patch.msp REINSTALL=ALL REINSTALLMODE=a It seems a bit cumbersome, will it work? :) Thanks again. -Original Message- From: Blair [mailto:os...@live.com] Sent: Monday, January 30, 2012 9:51 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! One way to see what the transforms in a patch actually contain WRT any particular MSI, open the MSI in Orca, then open the MSP file using the Transform menu item View a patch. It will highlight the database changes, and in the case of files, you can look at the two file-related tables to see which files it thinks have been changed. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Saturday, January 28, 2012 10:59 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] How does Torch decide which files changed?! One more thing, I opened the msp file with z7, there are only: exe dll (.net assemblies) and one txt file!? there. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 27, 2012 10:24 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! Torch marks up the database changes. Including -p causes it to leave the unchanged portions of the database intact so they will be present for Pyro to use in its processing. It is Pyro that looks at the two files and determines if they are the same or not, and it promotes files that compare as different to be considered as changed and thus be included with the other marked database changes. If you use WIXOUT or WIXPDB files then fragment boundaries are considered in the comparisons, so if you specify references to things to include in your patch family/families, things that are not in any referenced fragments are ignored (by design). Look for the files you are concerned with in the WIXMST file. You should find either paths or references to cabinet-ids for both the updated and the previous versions of the files. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 26, 2012 7:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How does Torch decide which files changed?! I'm creating a patch, I'm not sure that the patch includes all of my files even though I'm passing the -p flag to the torch.exe. Can someone please explain to me the logic that torch uses to determine what files are included in the patch. Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro
Re: [WiX-users] How does Torch decide which files changed?!
One more thing, I opened the msp file with z7, there are only: exe dll (.net assemblies) and one txt file!? there. -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 27, 2012 10:24 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! Torch marks up the database changes. Including -p causes it to leave the unchanged portions of the database intact so they will be present for Pyro to use in its processing. It is Pyro that looks at the two files and determines if they are the same or not, and it promotes files that compare as different to be considered as changed and thus be included with the other marked database changes. If you use WIXOUT or WIXPDB files then fragment boundaries are considered in the comparisons, so if you specify references to things to include in your patch family/families, things that are not in any referenced fragments are ignored (by design). Look for the files you are concerned with in the WIXMST file. You should find either paths or references to cabinet-ids for both the updated and the previous versions of the files. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 26, 2012 7:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How does Torch decide which files changed?! I'm creating a patch, I'm not sure that the patch includes all of my files even though I'm passing the -p flag to the torch.exe. Can someone please explain to me the logic that torch uses to determine what files are included in the patch. Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How does Torch decide which files changed?!
Thanks for the reply! I did find reference to a file I was concerned about... The problem is, that I changed the file locally on the customers machine, then I installed the patch, the file wasn't replaced... that led me to think that there was something wrong with the patch... By the way the file name appears 11 times in the wixmst file... Is there a way to create a patch that always replaces all the files it has? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 27, 2012 10:24 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] How does Torch decide which files changed?! Torch marks up the database changes. Including -p causes it to leave the unchanged portions of the database intact so they will be present for Pyro to use in its processing. It is Pyro that looks at the two files and determines if they are the same or not, and it promotes files that compare as different to be considered as changed and thus be included with the other marked database changes. If you use WIXOUT or WIXPDB files then fragment boundaries are considered in the comparisons, so if you specify references to things to include in your patch family/families, things that are not in any referenced fragments are ignored (by design). Look for the files you are concerned with in the WIXMST file. You should find either paths or references to cabinet-ids for both the updated and the previous versions of the files. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 26, 2012 7:19 AM To: wix-users@lists.sourceforge.net Subject: [WiX-users] How does Torch decide which files changed?! I'm creating a patch, I'm not sure that the patch includes all of my files even though I'm passing the -p flag to the torch.exe. Can someone please explain to me the logic that torch uses to determine what files are included in the patch. Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How does Torch decide which files changed?!
I'm creating a patch, I'm not sure that the patch includes all of my files even though I'm passing the -p flag to the torch.exe. Can someone please explain to me the logic that torch uses to determine what files are included in the patch. Thanks. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] creating a WIX small or minor patch
Found Paraffin! http://www.wintellect.com/CS/blogs/jrobbins/archive/2010/08/31/zen-of-paraffin.aspx I think that this is what I need! So that my HEAT won't generate different GUIDs each time. Are you familiar with it? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the ComponentRef Id=SampleComponent/ from within the PatchFamily Id='SamplePatchFamily' Version='1.0.0.0' Supersede='yes' tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor
Re: [WiX-users] creating a WIX small or minor patch
Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used * as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If no on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id=RTM for PatchBaseline\@Id. PatchBaseline Id=SP3 / -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but
Re: [WiX-users] creating a WIX small or minor patch
Yea, I got that, Thanks. What I meant was that I can use the same Guid for the Product ID and the UpgradeCode as the example do. That way I won't have to open the MSI with ORCA and find the generated Product ID Guid. But anyway, it doesn't help :( I really don't understand the problem... I take 2 wixpdb files that where generated during 2 different builds of the same product, the later one has a change somewhere in the code. All I want it to generate the patch, I don't mind if the patch will include all the .NET assemblies and not only the changed ones - since I know every build they are different. Thanks for the fast replay - any help will be appreciated greatly! P.S I'm trying to find an official Microsoft representative that can grant our company (we are a Microsoft gold partner) consulting hours for this issue. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means generate me a guid at build time - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used * as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If no on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to
Re: [WiX-users] creating a WIX small or minor patch
One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means generate me a guid at build time - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used * as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If no on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install)
Re: [WiX-users] creating a WIX small or minor patch
I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the ComponentRef Id=SampleComponent/ from within the PatchFamily Id='SamplePatchFamily' Version='1.0.0.0' Supersede='yes' tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an unpacked MSI but I believe the media number would still need to be higher than the highest file id in the MSI file table. The patch itself will contain cabinets for the altered files using the media cabinet name. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 13:01 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch One more thing I remembered, in our MSIs we don't use CAB, we just create a folder next to the MSI, it's easier for us to replace/fix text/config files after a build was already create... Does this influence the patch.wxs? I see that there is a Media tag that points to a cab file... -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 11:35 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The product code and the upgrade code are 2 different things. Don't mix them up. You can get the product code from the property table of the original MSI. Just open it in Orca or InstEd. The * means generate me a guid at build time - it isn't actually stored as a *. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 08:23 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, I tried replacing the * with the UpgradeCode Guid. Still the same errors... I must say the erros seem to be related to the fact that the patch.wxs has nothing to do with the build diff.wixmst generated from the 2 winxobj... Anyway I have products installed at customers already with the * in the product Id, how do I get the Guid that was generated for those MSIs? Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used * as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the
Re: [WiX-users] creating a WIX small or minor patch
Hi,
Yes, I think you are right, I got this when running the command you suggested:
MSI (s) (F8:34) [08:51:01:014]: SELMGR: ComponentId
'{9CD3A290-0DD5-4416-85D1-4781D9C8C0B6}' is registered to feature
'ProductFeature', but is not present in the Component table. Removal of
components from a feature is not supported!
I think it has to do with the fact that we are using HeatDirectory to harvest
the files, each component gets a different GUID every build... right?
So I'll have to look for a way to keep the IDs consistent over builds...
Thanks again.
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, January 24, 2012 4:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating a WIX small or minor patch
I don't think your problems are related to patch building. I think your second
MSI is not a valid minor update.
Try running the second MSI as an upgrade of the first one using the command
line mentioned in Rob's blog
http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg
rade-in-MSI-Use
I think you'll get some similar errors in the log.
If this is the case, you go through the MSDN sections mentioned on making minor
upgrades and check both of your MSIs to ensure you're following all the rules -
they are quick tricky. Comparing the two MSIs by looking at them in Orca rather
than by looking at the code so you can see what's actually been generated.
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Sent: 24 January 2012 14:00
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] creating a WIX small or minor patch
I see, the other reason we don't compress into cab is time, since we compress
everything into RARs for client delivery... so a cab will be redundant. But
point taken, I won't let anyone change a thing :).
To the main problem... I still can't seem to be able to run the Pyro command no
matter what...
After taking your advice I removed the ComponentRef Id=SampleComponent/
from within the PatchFamily Id='SamplePatchFamily' Version='1.0.0.0'
Supersede='yes' tag
And then I did get errors referring to my files, that is progress... but the
errors are as mentioned before:
C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM
patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version
3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved.
pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not
recommended because the patch cannot be uninstalled nor can it be sequenced
along with other patches for the target product.
See http://msdn2.microsoft.com/library/aa367571.aspx for more information.
E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 :
Removing component 'QsConfig.exe' from feature 'ProductFeature' is not
supported. Either the component was removed or the guid changed. Add the
component back, undo the change to the component guid, or remove the entire
feature.
The first section is:
Changing the ProductCode in a patch is not recommended because the patch cannot
be uninstalled nor can it be sequenced along with other patches for the target
product.
See http://msdn2.microsoft.com/library/aa367571.aspx for more information
I understand, I won't change the product ID between builds.
The second part:
E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 :
Removing component 'QsConfig.exe' from feature 'ProductFeature' is not
supported. Either the component was removed or the guid changed. Add the
component back, undo the change to the component guid, or remove the entire
feature.
That I don't understand, I didn't remove anything, maybe they are getting
different ids!? Both MSIs I used to generate the diff.wixmst are the same
except for some code change in one of the assemblies...
Thanks again!
-Original Message-
From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Sent: Tuesday, January 24, 2012 3:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] creating a WIX small or minor patch
That would invalidate the MSI if you don't keep the relevant tables up to date
too. Its not a recommended practice - do a proper build instead.
I've not built a patch targeting an unpacked MSI but I believe the media number
would still need to be higher than the highest file id in the MSI file table.
The patch itself will contain cabinets for the altered files using the media
cabinet name.
-Original Message-
From: tome...@qualisystems.com [mailto:tome...@qualisystems.com]
Sent: 24 January 2012 13:01
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] creating a WIX small or minor patch
One more thing I remembered, in our MSIs we don't use CAB, we just create a
folder next to the MSI, it's easier for us to replace/fix text/config files
after a build was already
Re: [WiX-users] creating a WIX small or minor patch
Hi again. Take a look at this WixHarvest.targets file. As far as I see I do pass the HeatGenerateGuidsNowtrue/HeatGenerateGuidsNow... I thought that this should keep the GUIDs consistent between builds... I'm wrong. Project DefaultTargets=Build xmlns=http://schemas.microsoft.com/developer/msbuild/2003; Import Project=$(WixTargetsPath) / PropertyGroup HeatGenerateGuidsNowtrue/HeatGenerateGuidsNow HeatOutputFile$(ProjectDir)\files.wxs/HeatOutputFile HeatDirectoryRefIdProductFolder/HeatDirectoryRefId HeatKeepEmptyDirectoriestrue/HeatKeepEmptyDirectories /PropertyGroup Target Name=BeforeBuild HeatDirectory ToolPath=$(WixToolPath) GenerateGuidsNow=$(HeatGenerateGuidsNow) OutputFile=$(HeatOutputFile) Directory=$(HeatHarvestDirectory) ComponentGroupName=ProductFiles DirectoryRefId=$(HeatDirectoryRefId) KeepEmptyDirectories=$(HeatKeepEmptyDirectories) SuppressCom=true SuppressRootDirectory=true SuppressRegistry=true SuppressUniqueIds=true / /Target /Project -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 4:18 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch I don't think your problems are related to patch building. I think your second MSI is not a valid minor update. Try running the second MSI as an upgrade of the first one using the command line mentioned in Rob's blog http://robmensching.com/blog/posts/2007/1/4/Doing-a-small-update-or-minor-upg rade-in-MSI-Use I think you'll get some similar errors in the log. If this is the case, you go through the MSDN sections mentioned on making minor upgrades and check both of your MSIs to ensure you're following all the rules - they are quick tricky. Comparing the two MSIs by looking at them in Orca rather than by looking at the code so you can see what's actually been generated. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 24 January 2012 14:00 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch I see, the other reason we don't compress into cab is time, since we compress everything into RARs for client delivery... so a cab will be redundant. But point taken, I won't let anyone change a thing :). To the main problem... I still can't seem to be able to run the Pyro command no matter what... After taking your advice I removed the ComponentRef Id=SampleComponent/ from within the PatchFamily Id='SamplePatchFamily' Version='1.0.0.0' Supersede='yes' tag And then I did get errors referring to my files, that is progress... but the errors are as mentioned before: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. The first section is: Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information I understand, I won't change the product ID between builds. The second part: E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. That I don't understand, I didn't remove anything, maybe they are getting different ids!? Both MSIs I used to generate the diff.wixmst are the same except for some code change in one of the assemblies... Thanks again! -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Tuesday, January 24, 2012 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That would invalidate the MSI if you don't keep the relevant tables up to date too. Its not a recommended practice - do a proper build instead. I've not built a patch targeting an
Re: [WiX-users] creating a WIX small or minor patch
I did have a Product Id=* So the problem was that the patched MSI and the original one had different Product Id. I thought that the UpgradeCode is the only important parameter... I'll give it a try anyway :) Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 23, 2012 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch Have you used * as the product code guid ? If so, youll need to change the updated MSI's product code to match the originals and rebuild. Removing a component in a minor update/patch is not allowed. Usually you just leave the file there until the next major upgrade. You can also replace the file with a zero length file if necessary. -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 22 January 2012 06:41 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If no on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id=RTM for PatchBaseline\@Id. PatchBaseline Id=SP3 / -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com]
Re: [WiX-users] creating a WIX small or minor patch
Hi, Thanks for the replay, you are right, removing the children from the PatchFamily element does include everything. But now I have a new problems :) I get this error: C:\Sample_1pyro.exe -v patch\patch.wixmsp -out patch\patch.msp -t RTM patch\diff.wixmst Microsoft (R) Windows Installer Xml Patch Builder version 3.5.2519.0 Copyright (C) Microsoft Corporation. All rights reserved. pyro.exe : warning PYRO1099 : Changing the ProductCode in a patch is not recommended because the patch cannot be uninstalled nor can it be sequenced along with other patches for the target product. See http://msdn2.microsoft.com/library/aa367571.aspx for more information. E:\4\139\Sources\Setup\common\Wix\Base\files.wxs(62) : error PYRO0305 : Removing component 'QsConfig.exe' from feature 'ProductFeature' is not supported. Either the component was removed or the guid changed. Add the component back, undo the change to the component guid, or remove the entire feature. What does it mean? -Original Message- From: Blair [mailto:os...@live.com] Sent: Friday, January 20, 2012 1:35 AM To: 'General discussion for Windows Installer XML toolset.' Subject: Re: [WiX-users] creating a WIX small or minor patch Do you really need to exclude anything from your patch? Do you really need more than one PatchFamily? If no on both questions then remove all children from the PatchFamily element. No references means include everything. Otherwise you will need to examine the generated WXS files and ensure that the IDs are stable and include all of them that you intend to possibly upgrade. Blair -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: Thursday, January 19, 2012 5:44 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id=RTM for PatchBaseline\@Id. PatchBaseline Id=SP3 / -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe
Re: [WiX-users] creating a WIX small or minor patch
Sure. I got that. I did make sure that the placeholder id is the same, but then I still get the error. I'll attack a zip with all the relevant file. The FoundationClient.proj has all the parameters that are transferred to the BaseSetup.wixproj, then with the help of the HeatDirectory I Harvest and create the Files.wxs dynamically for each product. Thanks! Ask me if something is missing! Don't work too hard to understand, just ask! :) Thanks again -Original Message- From: Peter Marcu [mailto:peter.ma...@microsoft.com] Sent: Wednesday, January 18, 2012 10:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The problem is a mismatch between the PatchBaseline you have in the patch wxs and the baseline you are specifying to pyro to attach the transform to. The first argument after the -t is the baseline. If your patch targets RTM (your patch will apply to an RTM install) then you should have Id=RTM for PatchBaseline\@Id. PatchBaseline Id=SP3 / -t RTM out\patch\diff.wixmst -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 18, 2012 1:48 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch The pyro command looks OK. Could you post your torch, candle and light command lines and your patch wxs please ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 18 January 2012 08:02 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax:
Re: [WiX-users] creating a WIX small or minor patch
Hi, As far as I understand the pyro command takes the patch.wxs and the diff file generated with the torch command. The problem is that the diff file is generated from 2 wixpdb files and I don't know how to make my patch.wxs compatible... the right ID to pass has something to do with the diff file, the example works fine, but when I use the same technique on my wixpdb's I get the error mentioned below. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Wednesday, January 11, 2012 12:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch That is a example from one of our released products. The Id in the patchbaseline is something you invent and only appears otherwise on the pyro command line. Why do you say that your files are relevant ? -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 10 January 2012 11:21 To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] creating a WIX small or minor patch Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe
Re: [WiX-users] creating a WIX small or minor patch
Yea, that I got from the sample, the problem is that our build.wxs files are a bit more complicated than the example ones... We are using HearDirectory to create our file list, and the file list generated doesn't have a nice ID that I can reference too... What I really need is a good example, an example that shows how to work with real life scenarios... Thanks. -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Monday, January 09, 2012 6:02 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] creating a WIX small or minor patch This goes in the Patch element. !-- Id must be higher than any sequence number in the baseline msi's Media/File table. Cabinet must match the original cabinet file name. -- Media Id=5728 Cabinet=Product.cab !-- Id created for the patches' baseline. Referenced in the command line. -- PatchBaseline Id=SP3 / /Media -Original Message- From: tome...@qualisystems.com [mailto:tome...@qualisystems.com] Sent: 09 January 2012 15:31 To: wix-users@lists.sourceforge.net Subject: [WiX-users] creating a WIX small or minor patch HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. - - Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. SDL PLC is a public limited company registered in England and Wales. Registered number: 02675207. Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6 7DY, UK. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ WiX-users mailing list
[WiX-users] creating a WIX small or minor patch
HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Error-2819 while Adding New Dialogs.
HI all, I'm having problems creating a WIX small or minor patch... My wsx files that I use to create the installation use HeatDirectory to harvest the files I need to put in my MSI (I'm not using cab, it's in a folder besides the MSI), anyway, I have 2 versions of the installation MSI and the wixpdb files that go along with them, the problem I'm having is creating the right patch.wsx to work with the diff.wixmst I create with the torch... The call to this command: pyro.exe out\patch\patch.wixmsp -out out\patch\patch.msp -t RTM out\patch\diff.wixmst throws: pyro.exe : error PYRO0252 : No valid transforms were provided to attach to the patch. Check to make sure the transforms you passed on the command line have a matching baseline authored in the patch. Also, make sure there are differences between your target and upgrade. And it figures... I don't have an RTM id anywhere... please help... Any link to a patch.wsx sample with a bit MORE details will be MUCH appreciated. Tomer Cohen InSight Team Leader, RD QualiSystems 20 Hacarmel St. Ganey Tikva, Israel 55900 Fax: +972-77-9014099 phone: +972-77-9014094 Mobile: +972-52-3362846 Email: tome...@qualisystems.com Web: www.qualisystems.com QualiSystems | 20 Hacarmel St. Ganey Tikva, Israel 55900 Learn about our NEW Test Automation Solution - TestShell Studio Join our QA Test Automation Group on LinkedIn Standards of Excellence This email including any attachment may contain confidential and/or privileged information intended solely for the use of the specified addressee[s]. Its contents shall not be copied, reproduced, changed or communicated to another - either in whole or in part. If you have received this email or parts thereof in error we request that you immediately notify us and delete this email. -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
