Re: [WiX-users] Wixstdba: Not invoking right msi for 32 bit platform in uninstallation
In my stdba as shown above I have both 32 and 64 bit msi. I am able to install and uninstall my product on both platforms. Observation: When I install product, on UI, there is processing: label. Which shows the current processing module. During installation, it shows name of 32 bit msi and installation log file contain 32 bit msi name. During un-installation, it shows name of 64 bit msi instead of 32 bit. Which gives feeling that 64 bit msi is invoked instead of 32 bit msi during un-installation. and apart from default burn log file , two log files gets created. log file with 64 bit msi includes all log statements of msi and custom action. This behavior is observed only on 32 bit platform. with regards, CD -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wixstdba-Not-invoking-right-msi-for-32-bit-platform-in-uninstallation-tp7598029p7598206.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Managed Bootstrapper “Failed to resolve source for file” for .cab files
I think my bootstrapper does almost similar thing to what WiX toolset does(couldn't find any big difference in the .wxs file). I wrote event handler for ResolveSource event like this http://stackoverflow.com/a/14653902/678558 . But when I debug my bootstrapper, ResolveSource event is raised by every individual .cab file(even when there is no Payload element for any .cab file specified), so, if I don't specify Payload elements for each .cab file under MsiPackage element, my bootstrapper doesn't know the download url for each .cab file. And installation fails. It seems that my bootstrapper can't go through this ResolveSource event handler stage. (If I add Payload element for each .cab file under MsiPackage element, it downloads .cab files well and installation goes well, too.) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WiX-Managed-Bootstrapper-Failed-to-resolve-source-for-file-for-cab-files-tp7598023p7598208.html Sent from the wix-users mailing list archive at Nabble.com. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WiX Managed Bootstrapper “Failed to resolve source for file” for .cab files
Something is different. The WiX toolset works. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: sky [mailto:volon...@gmail.com] Sent: Sunday, November 23, 2014 9:27 PM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] WiX Managed Bootstrapper “Failed to resolve source for file” for .cab files I think my bootstrapper does almost similar thing to what WiX toolset does(couldn't find any big difference in the .wxs file). I wrote event handler for ResolveSource event like this http://stackoverflow.com/a/14653902/678558 . But when I debug my bootstrapper, ResolveSource event is raised by every individual .cab file(even when there is no Payload element for any .cab file specified), so, if I don't specify Payload elements for each .cab file under MsiPackage element, my bootstrapper doesn't know the download url for each .cab file. And installation fails. It seems that my bootstrapper can't go through this ResolveSource event handler stage. (If I add Payload element for each .cab file under MsiPackage element, it downloads .cab files well and installation goes well, too.) -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Does protocol=netfx works with .net 4.5.1 redist
Hi, I am trying to get progress of .net 4.5.1 package in my burn bootstrapper. Can anyone help out how to do this ? I tried protocol=netfx on the NetFx451 package and it doesn't work. Thanks Soundararajan -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
