Re: [WiX-users] Bundle upgrade rollback removes the entire product other than bundle ARP entry

Sure. Plan section of new bundle - [1910:00E8][2012-09-17T09:54:25]: Plan 15 packages, action: Install [1910:00E8][2012-09-17T09:54:25]: Skipping dependency registration on package with no dependency providers: VC8X86 [1910:00E8][2012-09-17T09:54:25]: Setting string variable 'WixBundleLog_VC8

Re: [WiX-users] Bundle upgrade rollback removes the entire product other than bundle ARP entry

Sure. Plan section of new bundle - [1910:00E8][2012-09-17T09:54:25]: Plan 15 packages, action: Install [1910:00E8][2012-09-17T09:54:25]: Skipping dependency registration on package with no dependency providers: VC8X86 [1910:00E8][2012-09-17T09:54:25]: Setting string variable 'WixBundleLog_VC8X86

[WiX-users] Bundle upgrade rollback removes the entire product other than bundle ARP entry

Hi, During bundled upgrade, if the uninstall of the old bundle fails, this invokes a rollback on MSI upgrade. This in turn causes the MSI to be uninstalled instead of just rolling back to re-install the previous version of MSI. The version of wix am using is 3.6.2803.0. Is this a known issue wit

[WiX-users] Feature state for related package during major upgrades in bundle

Hi, Am using a bundled installer to install major upgrades for a bunch of MSIs (that are installed using a bundle as well). While I can use DetectRelatedMsiPackage event to be informed about a major upgrade, I couldn't find a way to determine the state of individual features in the previous instal

[WiX-users] Extract MSIs from Burn generated EXE

Is it possible to extract MSIs bundled in a Burn EXE? If so, is there a recommended tool for that? Thanks, Shruthi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extract-MSIs-from-Burn-generated-EXE-tp6914823p6914823.html Sent from the wix-users ma

[WiX-users] BA Prereq installer UI

Hi, Is it possible to customize and localize the first UI screen that shows up if BA needs .Net and it isn't installed? Also, is there a way to provide localized versions of the .Net license in the wix variable "WixMbaPrereqLicenseUrl"? Thanks, Shruthi -- View this message in context: http://w

Re: [WiX-users] Unknown WiX variables in Bundle with WiX 3.6.1908.0

Is there a way to replace the prerequisite .Net install UI with just an notification to the user that they need to install a particular version of .Net before they can install the bundle? Thanks, Shruthi -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.c

Re: [WiX-users] How to cleanup folder created by Burn in temporary directory

Upgrading to a newer version (v3.6.2019) fixed this issue. Thank you! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-cleanup-folder-created-by-Burn-in-temporary-directory-tp6848834p6866287.html Sent from the wix-users mailing list archive at

Re: [WiX-users] Managed BA can't parse unknown args with spaces successfully

Thanks for your email and the link! That fix only fixed it in the native interface to BA. It is still an issue with the C# interface. I still repro the problem on build v3.6.2019.0 Please let me know if I should go ahead a log a bug. Thanks! Shruthi -- View this message in context: http://wind

[WiX-users] Managed BA can't parse unknown args with spaces successfully

Hi, Run bundle with the following command line args: setup.exe /q /INSTALLDIR="c:\dfds safds \sadfds" /SomeOtherParam Managed BA receives the following string for command line args: "/INSTALLDIR=c:\dfds safds \sadfds" /SomeOtherParam The space in the path causes invalid argument parsing in the BA

[WiX-users] How to cleanup folder created by Burn in temporary directory

Hi, Burn creates a folder containing assembly and configuration files of the custom bootstrapper application, both during installation and uninstallation. Is there a way to force this to be cleaned up once the operation is complete? In addition, is there a way to force an MSI (created from WIX) t

Re: [WiX-users] .Net pre-requisite check when using Managed Bootstrapper application in Burn

Doesn't the Bundle "Condition attribute" only support built in variables and not NETFRAMEWORK40FULL (or registry search results). In addition, it doesn't support custom error messages. Is this correct? I wasn't able to get a "Condition element" within a Bundle block to work. Is it possible that I

Re: [WiX-users] .Net pre-requisite check when using Managed Bootstrapper application in Burn

Wix setup also uses a managed bootstrapper. This basically allows us to use WPF UI to drive the bundle installation. Wix setup however bootstraps .Net install in the bundle. I would like to have some support in Burn that would allow me to fail the installation if the required .Net version isn't fou

Re: [WiX-users] Selectively uninstall features when using Burn

Rob, thanks so much for yor quick response! I was able to get selective uninstall to work. However, I discovered another issue with Burn feature selection in general (both install and uninstall case). I noticed that unless it's the first time installing the product or a complete uninstall, Burn do