Re: [WiX-users] Creating multiple Minor Updates
There's a major upgrade element you can use. Change ProductCode, PackageCode, increment ProductVersion somewhere in the first three digit fields, and sequence the RemoveExistingProducts immediately after InstallInitialize so that the older version is entirely uninstalled before the new one installs. Phil Wilson On Thu, Nov 14, 2013 at 12:45 PM, Nagesh Hora horanag...@gmail.com wrote: Thanks Blair and Phil, As we don't have fileversioning for already shipped binaries. best bet would be uninstalling previous package and installing the new package. How to force new .msi package to uninstall previous and install (Major upgrade) I need to change productcode, productversion, packagecode. Is that right??? Thanks Nagesh On Thu, Nov 14, 2013 at 12:28 AM, Blair Murri os...@live.com wrote: Nagesh, Phil is correct. See the file versioning rules on MSDN. http://msdn.microsoft.com/library/windows/desktop/aa368599.aspx -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, November 13, 2013 10:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name; Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating -multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch
Re: [WiX-users] Creating multiple Minor Updates
Thanks Blair and Phil, As we don't have fileversioning for already shipped binaries. best bet would be uninstalling previous package and installing the new package. How to force new .msi package to uninstall previous and install (Major upgrade) I need to change productcode, productversion, packagecode. Is that right??? Thanks Nagesh On Thu, Nov 14, 2013 at 12:28 AM, Blair Murri os...@live.com wrote: Nagesh, Phil is correct. See the file versioning rules on MSDN. http://msdn.microsoft.com/library/windows/desktop/aa368599.aspx -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, November 13, 2013 10:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating -multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting
Re: [WiX-users] Creating multiple Minor Updates
Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users . -- Thanks Regards, Chaitanya. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users . -- Thanks Regards, Chaitanya. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
Is there any way to unsubscribe from this mailing list? -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, November 13, 2013 10:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating -multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users . -- Thanks Regards, Chaitanya. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP
Re: [WiX-users] Creating multiple Minor Updates
At the bottom of every e-mail, there is this link where you can do it: https://lists.sourceforge.net/lists/listinfo/wix-users See the bottom of the page; put your e-mail address there and unsubscribe. -Original Message- From: Jacky Liang [mailto:jli...@kierantimberlake.com] Sent: Wednesday, November 13, 2013 10:53 To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates Is there any way to unsubscribe from this mailing list? -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, November 13, 2013 10:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating -multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list
Re: [WiX-users] Creating multiple Minor Updates
Nagesh, Phil is correct. See the file versioning rules on MSDN. http://msdn.microsoft.com/library/windows/desktop/aa368599.aspx -Original Message- From: Phil Wilson [mailto:phildgwil...@gmail.com] Sent: Wednesday, November 13, 2013 10:39 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Creating multiple Minor Updates You need to increment the file versions for patched files, basically because updates are based on them. http://msdn.microsoft.com/en-us/library/aa367835(v=vs.85).aspx Something like REINSTALLMODE=amus is not a good idea. If you have included merge modules from 3rd parties, or Microsoft merge modules then congratulations, you may have just downgraded some fix that was applied by overwriting the higher versioned fix with yours, and maybe even re-opened a security vulnerability. That danger may be less with a patch containing only your files, but it's a bad habit to start when the right answer is simply to increment your file versions. Phil Wilson On Wed, Nov 13, 2013 at 7:21 AM, Chaitanya chaita...@pointcross.com wrote: Add a Tag in Property tag Property Id='REINSTALLMODE' Value='amus'/ On 13-11-2013 20:46, Nagesh Hora wrote: Thanks Blair... When i apply the patch. I don't see the changed .dll applied. On going through the logs i see below log. MSI (s) (14:74) [23:44:05:695]: File:Component Name;Won't Overwrite;Won't patch;Existing file is of an equal version Do I have to change version for each changed component Thanks Nagesh On Wed, Nov 13, 2013 at 1:13 AM, Blair Murri os...@live.com wrote: It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating -multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.c lktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users . -- Thanks Regards, Chaitanya
Re: [WiX-users] Creating multiple Minor Updates
I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
It is anticipated that most products will not need to reference anything because they wish to update all changes, and the default if you don't specify anything in your filter is to include all changes. If you need to filter your changes to only include some of them, then you reference items and all changes in the self-same fragments are included while all changes in unreferenced fragments are ignored. That is not the expected use case for most products. -Blair Date: Tue, 12 Nov 2013 18:42:03 -0800 From: horanag...@gmail.com To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Creating multiple Minor Updates I am more confused now. Do we have to mention changed binaries (.dlls, .ocxs, .exes) in component reference... Please someone help here, how to do perfect patch?? I followed steps in Wix 3.5 tutorial, without luck.. Any help would be appreciated. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590613.html Sent from the wix-users mailing list archive at Nabble.com. -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- DreamFactory - Open Source REST JSON Services for HTML5 Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
It is expected that for most products you never need more than one PatchFamily and you NEVER need to reference anything inside of it (which will then update all changes (and nothing except the changes) between the two MSIs). Blair From: TimM Sent: Tuesday, October 29, 2013 11:58 AM To: General discussion for Windows Installer XML toolset. Joe, we are just looking at patches and I have a question about this method if you don't mind? I am just testing out with using the sample 'Using Pure WiX' example and I am looking at the PatchFamily element and noticed that you have to add a reference to a component in your main install project. And then you mentioned that you added a new file so in the 2nd patch added the reference to the new component. So my question is do you have to add a reference to all components that changed or do you simply have to add a reference to any component that resides in your target project and then the patch will pick up all changed/updated components? The reason I ask is because in doing the example the sample.txt file updated fine, so I added some .exe files to the sample target and update projects, some that changed and some that did not and I left the ComponentRef in the patch.wxs to still be the same. Did not add any more references. I then built the patch and when I ran it over the target install it correctly upgraded all files that were updated and left all the ones that were the same as is. So it seems to work that way. So was that just a side effect and it was not suppose to do that or is that how it is supposed to work? I have not tried to create a cumulative patch from this example, but if it does work this way then for a 2nd and 3rd patch would you have to add more component references or simply build the cumulative patch and it would only be new components that you would have to add as references? Oh and that does bring up the question on how you built the cumulative patch? what command line do you use to build with to generate the patch to work over 1 and ver 2, and so on? Thanks for any insight that you can supply. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590098.html Sent from the wix-users mailing list archive at Nabble.com. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
Joe, we are just looking at patches and I have a question about this method if you don't mind? I am just testing out with using the sample 'Using Pure WiX' example and I am looking at the PatchFamily element and noticed that you have to add a reference to a component in your main install project. And then you mentioned that you added a new file so in the 2nd patch added the reference to the new component. So my question is do you have to add a reference to all components that changed or do you simply have to add a reference to any component that resides in your target project and then the patch will pick up all changed/updated components? The reason I ask is because in doing the example the sample.txt file updated fine, so I added some .exe files to the sample target and update projects, some that changed and some that did not and I left the ComponentRef in the patch.wxs to still be the same. Did not add any more references. I then built the patch and when I ran it over the target install it correctly upgraded all files that were updated and left all the ones that were the same as is. So it seems to work that way. So was that just a side effect and it was not suppose to do that or is that how it is supposed to work? I have not tried to create a cumulative patch from this example, but if it does work this way then for a 2nd and 3rd patch would you have to add more component references or simply build the cumulative patch and it would only be new components that you would have to add as references? Oh and that does bring up the question on how you built the cumulative patch? what command line do you use to build with to generate the patch to work over 1 and ver 2, and so on? Thanks for any insight that you can supply. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Creating-multiple-Minor-Updates-tp7586073p7590098.html Sent from the wix-users mailing list archive at Nabble.com. -- Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Creating multiple Minor Updates
Your patch wix looks similar to mine but we use @MinorUpdateTargetRTM=yes
on the patch element as that is what you are doing it may be worth a go.
-Original Message-
From: Joe Flynn [mailto:roo...@gmail.com]
Sent: 22 May 2013 20:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating multiple Minor Updates
Hi All,
I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.1 Description=Update for MyProduct 6.100.1
DisplayName=MyProduct 6.100.1 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1000 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.1
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
Everything is updated as expected when I apply this patch (MSP). I now want
to create a second patch, containing an additional file. This will be version
6.100.2, and I plan on making this cumulative, so that one could apply
6.100.2 and get the content of 6.100.1 as well. Below is the patch.wxs file
for my 6.100.2 update:
==
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.2 Description=Update for MyProduct 6.100.2
DisplayName=MyProduct 6.100.2 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1001 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.2
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.dll /
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
The patch builds as expected, and will apply to 6.100.0 without issue. The
problem arises when I attempt to go from 6.100.1 - 6.100.2. I get the below
error in my MSI.LOG file, and the patch is not applied:
==
MSI (c) (60:50) [11:22:56:067]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp has a digital signature MSI (c) (60:50)
[11:22:56:070]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp is permitted to run at the 'unrestricted'
authorization level.
MSI (c) (60:50) [11:22:56:070]: SequencePatches starts. Product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, Product version: 6.100.0.0, Upgrade
code: {7D1500B3-D638-4213-9772-894096C84768}, Product language 1033 MSI (c)
(60:50) [11:22:56:071]: Full optimizations are not possible in the patch
sequencer because new patch[es] had been added in the current transaction.
MSI (c) (60:50) [11:22:56:071]: Applicability checks need to be performed in
this transaction because new, 3.0 minor update patch[es] have been provided.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the applicability
of minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993}
against product code: {604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.0.0, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Transform 'SEGPatch.1'
is valid.
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI
(c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI (c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
{B7C830A9-E120-48ED-BCC2-00C8989A5993} is applicable.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the applicability
of minor upgrade patch C:\Public\Hotfix\EG\eguide_2.msp against product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.1.7000, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Note: 1: 2749 2:
SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: 1: 2749 2: SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
C:\Public\Hotfix\EG\eguide_2.msp is not applicable.
MSI (c) (60:50) [11:22:56:071]: The #_QFESequence table with patches sorted
on Sequence within Patch Families:
MSI (c) (60:50) [11:22:56:071]: PatchGUID:
{B7C830A9-E120-48ED-BCC2-00C8989A5993} PatchFamily: SEGPatchFamily Sequence
Re: [WiX-users] Creating multiple Minor Updates
David,
Thank you very much, after adding @MinorUpdateTargetRTM=yes everything is
working perfectly.
Joe
On Thu, May 23, 2013 at 5:50 AM, David Watson dwat...@sdl.com wrote:
Your patch wix looks similar to mine but we use @MinorUpdateTargetRTM=yes
on the patch element as that is what you are doing it may be worth a go.
-Original Message-
From: Joe Flynn [mailto:roo...@gmail.com]
Sent: 22 May 2013 20:01
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating multiple Minor Updates
Hi All,
I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.1 Description=Update for MyProduct 6.100.1
DisplayName=MyProduct 6.100.1 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1000 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.1
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
Everything is updated as expected when I apply this patch (MSP). I now want
to create a second patch, containing an additional file. This will be
version
6.100.2, and I plan on making this cumulative, so that one could apply
6.100.2 and get the content of 6.100.1 as well. Below is the patch.wxs file
for my 6.100.2 update:
==
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.2 Description=Update for MyProduct 6.100.2
DisplayName=MyProduct 6.100.2 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1001 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.2
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.dll /
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
The patch builds as expected, and will apply to 6.100.0 without issue. The
problem arises when I attempt to go from 6.100.1 - 6.100.2. I get the
below
error in my MSI.LOG file, and the patch is not applied:
==
MSI (c) (60:50) [11:22:56:067]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp has a digital signature MSI (c) (60:50)
[11:22:56:070]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp is permitted to run at the 'unrestricted'
authorization level.
MSI (c) (60:50) [11:22:56:070]: SequencePatches starts. Product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, Product version: 6.100.0.0, Upgrade
code: {7D1500B3-D638-4213-9772-894096C84768}, Product language 1033 MSI (c)
(60:50) [11:22:56:071]: Full optimizations are not possible in the patch
sequencer because new patch[es] had been added in the current transaction.
MSI (c) (60:50) [11:22:56:071]: Applicability checks need to be performed
in
this transaction because new, 3.0 minor update patch[es] have been
provided.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the
applicability
of minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993}
against product code: {604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.0.0, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Transform
'SEGPatch.1'
is valid.
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Tables 3: -2147287038 MSI
(c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Columns 3: -2147287038 MSI
(c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
{B7C830A9-E120-48ED-BCC2-00C8989A5993} is applicable.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the
applicability
of minor upgrade patch C:\Public\Hotfix\EG\eguide_2.msp against product
code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.1.7000, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922 MSI (c) (60:50) [11:22:56:071]: Note: 1: 2749 2:
SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: 1: 2749 2: SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000 MSI (c)
(60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
C
[WiX-users] Creating multiple Minor Updates
Hi All,
I have created a product MSI which is versioned 6.100.0 . I have then
successfully created a minor update which installs as 6.100.1. Below is the
patch.wxs file I use to accomplish this:
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.1 Description=Update for MyProduct 6.100.1
DisplayName=MyProduct 6.100.1 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1000 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.1
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
Everything is updated as expected when I apply this patch (MSP). I now want
to create a second patch, containing an additional file. This will be
version 6.100.2, and I plan on making this cumulative, so that one could
apply 6.100.2 and get the content of 6.100.1 as well. Below is the
patch.wxs file for my 6.100.2 update:
==
?xml version=1.0 encoding=utf-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Patch AllowRemoval=yes Classification=Update Comments=Patch for
MyProduct 6.100.2 Description=Update for MyProduct 6.100.2
DisplayName=MyProduct 6.100.2 Software Patch Manufacturer=MyCompany
MoreInfoURL=http://www.mycompany.com;
Media Id=1001 Cabinet=SEGPatch.cab
PatchBaseline Id=SEGPatch /
/Media
PatchFamily Id=SEGPatchFamily Version=6.100.2
ProductCode=604F30E1-35F2-4E34-AA21-3E83CDE863E1 Supersede=yes
ComponentRef Id=CMP_ProjectElements.dll /
ComponentRef Id=CMP_ProjectElements.Forms.dll /
/PatchFamily
/Patch
/Wix
==
The patch builds as expected, and will apply to 6.100.0 without issue. The
problem arises when I attempt to go from 6.100.1 - 6.100.2. I get the
below error in my MSI.LOG file, and the patch is not applied:
==
MSI (c) (60:50) [11:22:56:067]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp has a digital signature
MSI (c) (60:50) [11:22:56:070]: SOFTWARE RESTRICTION POLICY:
C:\Public\Hotfix\EG\eguide_2.msp is permitted to run at the 'unrestricted'
authorization level.
MSI (c) (60:50) [11:22:56:070]: SequencePatches starts. Product code:
{604F30E1-35F2-4E34-AA21-3E83CDE863E1}, Product version: 6.100.0.0, Upgrade
code: {7D1500B3-D638-4213-9772-894096C84768}, Product language 1033
MSI (c) (60:50) [11:22:56:071]: Full optimizations are not possible in the
patch sequencer because new patch[es] had been added in the current
transaction.
MSI (c) (60:50) [11:22:56:071]: Applicability checks need to be performed
in this transaction because new, 3.0 minor update patch[es] have been
provided.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the
applicability of minor upgrade patch {B7C830A9-E120-48ED-BCC2-00C8989A5993}
against product code: {604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.0.0, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922
MSI (c) (60:50) [11:22:56:071]: Transform 'SEGPatch.1' is valid.
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
{B7C830A9-E120-48ED-BCC2-00C8989A5993} is applicable.
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: verifying the
applicability of minor upgrade patch C:\Public\Hotfix\EG\eguide_2.msp
against product code: {604F30E1-35F2-4E34-AA21-3E83CDE863E1}, product
version: 6.100.1.7000, product language 1033 and upgrade code:
{7D1500B3-D638-4213-9772-894096C84768}
MSI (c) (60:50) [11:22:56:071]: Validating transform 'SEGPatch.1' with
validation bits 0x922
MSI (c) (60:50) [11:22:56:071]: Note: 1: 2749 2: SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000
MSI (c) (60:50) [11:22:56:071]: 1: 2749 2: SEGPatch.1 3:
C:\Public\Hotfix\EG\eguide_2.msp 4: 6.100.0.2789 5: 6.100.1.7000
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
C:\Public\Hotfix\EG\eguide_2.msp is not applicable.
MSI (c) (60:50) [11:22:56:071]: The #_QFESequence table with patches sorted
on Sequence within Patch Families:
MSI (c) (60:50) [11:22:56:071]: PatchGUID:
{B7C830A9-E120-48ED-BCC2-00C8989A5993} PatchFamily: SEGPatchFamily Sequence:
6.100.1 SequenceOrder: 0 Type: minor upgrade
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
{B7C830A9-E120-48ED-BCC2-00C8989A5993} cannot be superseded because there
is no supersedence defined in SEGPatchFamily family yet for this type
MSI (c) (60:50) [11:22:56:071]: PATCH SEQUENCER: minor upgrade patch
