Re: [WiX-users] WcaAddTempRecord - S_OK but no results - how to debug?
My apologies again! It was a dumb typo on my part. As I was pasting an example of my code into the editor to post here, I realized that the last parameter of WcaAddTempRecord should be a ComponentId, and I had used the Id of my custom xml element. Changing that parameter to the Id of the component, now results in the registry key being written. There is still some issue with the formatting of my binary string, which I tried to prepend with L#X in the byte array, but I can go back to the debugger and sore that out, now that the general functionality is working. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WcaAddTempRecord-S-OK-but-no-results-how-to-debug-tp7600691p7600692.html Sent from the wix-users mailing list archive at Nabble.com. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WcaAddTempRecord - S_OK but no results - who to debug?
I am looking for advice on how to sort out a problem I having using WcaAddTempRecord. My immediate CA creates a BYTE array (an encrypted 'blob') which I need to write to the Registry as a REG_BINARY type value. I am trying to use WcaAddTempRecord to the Registry table, ( using the code in wix src\ext\GamingExtension\ca\caming.cpp WriteGameExplorerRegistry as an example implementation). I can step through into WcaAddTempRecord (src\libs\wcautil\wcawrap) and it all appears to step through the columns adding the data successfully, and does not report any error. (When I first read through the code I was concerned about the comment that binary streams are not supported, but when trying to add a binary registry value that 'else' block is not hit. So I assume that the comment does not relate to adding a binary registry value.) I also found the temp named msi file and tried to inspect it with orca, after stepping past the WcaAddTempRecord call, but before running the script phase of the install, and I did not find the temporary row entry. I noticed a binary .ipi file so maybe that is where this info is held. The bottom line is that the registry value is never created, even though WcaAddTempRecord does not report any error. I also provided a variable for the MSIDBERROR dbError parameter, which was NULL in the gaming implementation. The verbose log, with the MSI debug value set to 7, indicates that the immediate CA is called and returns successfully, but I cannot find anything in the log related to the added temporary Registry table row, or the 'uniquified' ID generated in WcaAddTempRecord, etc. I also changed my code to write a string registry value, but I could not find anything related to that temporary entry either. I am looking for clues on how to track down whether the temporary row was created in the msi, or why I cannot find the entry in the registry. Thanks for any advice. (My schedule in the next few days may prevent me posting a response but I do appreciate the input.) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WcaAddTempRecord-S-OK-but-no-results-who-to-debug-tp7600691.html Sent from the wix-users mailing list archive at Nabble.com. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] When is Wix 3.10 publicly available ?
See these blog posts. Both of these have a note about progress on 3.10 https://www.firegiant.com/blog/2015/6/2/wix-online-meeting-68-highlights/ https://www.firegiant.com/blog/2015/6/16/wix-online-meeting-70-highlights/ On 22 June 2015 at 17:55, Rob Mensching r...@firegiant.com wrote: PS: WiX v3.10 is available now: http://wixtoolset.org/releases/ ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Monday, June 22, 2015 5:07 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] When is Wix 3.10 publicly available ? Those issues are discussed in the weekly on-line meeting, Tuesday evening, and summarized in this blog https://www.firegiant.com/blog/2015/6/16/wix-online-meeting-70-highlights/ . If I recall from the comments in the last meeting, the 'RC' will be announced soon. The stable release is expected to wait until after the Microsoft release of VS2015 is completed. Subsequently it is likely that there will be 'service releases' of 3.10.n rather than a focus on a 3.11 (or 3.1x) and a focus on the 4.x efforts. But those are issues which are discussed in the weekly meeting on, Tuesday evening, and I think all are welcome to participate. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install
While doing other research I came across these threads, and made note of them in the event that I might need them in the future. They might be helpful to you: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Resume-Installation-Plan-td7579146.html http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-restore-after-reboot-not-working-td7585217.html#a7585250 -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600690.html Sent from the wix-users mailing list archive at Nabble.com. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install
Thank you, Phil. Unfortunately, I only have one MSI that installs both my application and ext2fsd. Are you suggesting that I split them up into two MSIs and then bundle them using Burn? Thank you. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600693.html Sent from the wix-users mailing list archive at Nabble.com. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Reboot required during major upgrade in-between uninstall and re-install
I guess I misread your question and assumed that you were using Burn. Given that I came across those posts I thought they might be helpful but if you are not using Burn I can't really make any suggestion. I have only used the approach of putting each app and each driver in a separate UI-less MSI and then chaining them using Burn. I have some bundles which have several hundred msi packages in the chain and I find that this approach works well for me. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Reboot-required-during-major-upgrade-in-between-uninstall-and-re-install-tp7600688p7600695.html Sent from the wix-users mailing list archive at Nabble.com. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to Allow Same Version Upgrades in Bundles
I'm trying to implement same version upgrades in our bootstrapper. We build our product in one build process and later create the installers in a second package process. This allows us to repackage our product when fixing installer changes that do not affect the product in any other way. We do not change our versions when we repackage. I found that instead of upgrading the existing bundle installation, the new bundle is installed separately resulting in two ARP entries. I found feature http://wixtoolset.org/issues/3746/ requesting that burn support same version upgrades. Feature 3746 is listed as Untriaged and had been opened for a very long time. I expect this means an official fix is not coming soon. Are there any workarounds for supporting same version upgrades in bundles? -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Allow Same Version Upgrades in Bundles
Any BA can choose to allow same version upgrades. The wixstdba does not. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Tuesday, June 23, 2015 1:58 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to Allow Same Version Upgrades in Bundles I'm trying to implement same version upgrades in our bootstrapper. We build our product in one build process and later create the installers in a second package process. This allows us to repackage our product when fixing installer changes that do not affect the product in any other way. We do not change our versions when we repackage. I found that instead of upgrading the existing bundle installation, the new bundle is installed separately resulting in two ARP entries. I found feature http://wixtoolset.org/issues/3746/ requesting that burn support same version upgrades. Feature 3746 is listed as Untriaged and had been opened for a very long time. I expect this means an official fix is not coming soon. Are there any workarounds for supporting same version upgrades in bundles? -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Allow Same Version Upgrades in Bundles
Not today. Creating the same bundle with the same version just isn't something wixstdba considers a real scenario today. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Tuesday, June 23, 2015 3:06 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] How to Allow Same Version Upgrades in Bundles Conversely, is there a way to DISALLOW same version upgrades in bundles using wixstdba? I'm trying to figure out what my options are. -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Allow Same Version Upgrades in Bundles
Conversely, is there a way to DISALLOW same version upgrades in bundles using wixstdba? I'm trying to figure out what my options are. On Tue, Jun 23, 2015 at 2:32 PM, Rob Mensching r...@firegiant.com wrote: Any BA can choose to allow same version upgrades. The wixstdba does not. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Tuesday, June 23, 2015 1:58 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to Allow Same Version Upgrades in Bundles I'm trying to implement same version upgrades in our bootstrapper. We build our product in one build process and later create the installers in a second package process. This allows us to repackage our product when fixing installer changes that do not affect the product in any other way. We do not change our versions when we repackage. I found that instead of upgrading the existing bundle installation, the new bundle is installed separately resulting in two ARP entries. I found feature http://wixtoolset.org/issues/3746/ requesting that burn support same version upgrades. Feature 3746 is listed as Untriaged and had been opened for a very long time. I expect this means an official fix is not coming soon. Are there any workarounds for supporting same version upgrades in bundles? -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] How to Uninstall ExePackage Only During Uninstall
My ExePackage gets uninstalled during upgrades and I'd like to only uninstall during an actual uninstall. Any suggestions on how I might go about doing this? I was hoping I could do something in my bafunctions.dll but I'm hitting a wall in my brainstorming. My bundle consists of the following: * A few pre-requisites (A) that will remain on the system after uninstall * A pre-requisite ExePackage (B) that will be uninstalled only when my product MSI is uninstalled * My product MSI (C) The package order in the chain is as follows: chain PackageGroupRef Id=A/ PackageGroupRef Id=B/ PackageGroupRef Id=C/ /chain B is an ExePackage that has DetectCondition and InstallCondition set. During an install or uninstall the packages run in the expected order: * Install: A, B, C * Uninstall: C, B However, during an upgrade I get an undesired order. A and B are not upgraded because they are detected as already existing at the correct version. C is upgraded to the new version. The last thing the new bundle does is to uninstall the related bundle. In the log for the related bundle uninstall I see that B is marked as Obsolete so it is uncached and unregistered. BUT C is detected as Present and is thus selected to be uninstalled. * Upgrade: C, UninstallRelatedBundle(B) I'd like to only uninstall B when C is uninstalled. I think I have my DetectCondition setup properly to install B when the new bundle contains a new version of B. However, I never want to uninstall B during an upgrade. B should be uninstalled only during an uninstall. -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] How to Uninstall ExePackage Only During Uninstall
Give it a Provides element from Dependency Extension to enable reference tracking. ___ FireGiant | Dedicated support for the WiX toolset | http://www.firegiant.com/ -Original Message- From: Edwin Castro [mailto:egca...@gmail.com] Sent: Tuesday, June 23, 2015 4:06 PM To: General discussion for Windows Installer XML toolset. Subject: [WiX-users] How to Uninstall ExePackage Only During Uninstall My ExePackage gets uninstalled during upgrades and I'd like to only uninstall during an actual uninstall. Any suggestions on how I might go about doing this? I was hoping I could do something in my bafunctions.dll but I'm hitting a wall in my brainstorming. My bundle consists of the following: * A few pre-requisites (A) that will remain on the system after uninstall * A pre-requisite ExePackage (B) that will be uninstalled only when my product MSI is uninstalled * My product MSI (C) The package order in the chain is as follows: chain PackageGroupRef Id=A/ PackageGroupRef Id=B/ PackageGroupRef Id=C/ /chain B is an ExePackage that has DetectCondition and InstallCondition set. During an install or uninstall the packages run in the expected order: * Install: A, B, C * Uninstall: C, B However, during an upgrade I get an undesired order. A and B are not upgraded because they are detected as already existing at the correct version. C is upgraded to the new version. The last thing the new bundle does is to uninstall the related bundle. In the log for the related bundle uninstall I see that B is marked as Obsolete so it is uncached and unregistered. BUT C is detected as Present and is thus selected to be uninstalled. * Upgrade: C, UninstallRelatedBundle(B) I'd like to only uninstall B when C is uninstalled. I think I have my DetectCondition setup properly to install B when the new bundle contains a new version of B. However, I never want to uninstall B during an upgrade. B should be uninstalled only during an uninstall. -- Edwin G. Castro -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -- Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical virtual servers, alerts via email sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
