Re: [WiX-users] Help with BA Programming

Dan, If you only have one msi, you probably don't need to utilize a bootstrapper application. The only time you'd need to utilize the BA is if you want to chain multiple msi's. It sounds like you only have one installer. You can create any kind of MBA to interface with the given bootstrapper appl

Re: [WiX-users] Getting current downloading package name in BA for Web installer

Look through the log files to see why the uninstall for the msi's didn't go through. If the Bundle was uninstalled, there has to be a log file detailing the actions of each MSI. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Getting-current-downl

Re: [WiX-users] Bootstrapper question

remove the UI from genius and create one with your own MBA. Use these properties, and send them down to msi's -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-question-tp7593254p7593478.html Sent from the wix-users mailing list archive

Re: [WiX-users] Changing the condition of an existing action.

You can use orca to open and edit the msi. You can change the condition of it as well. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Changing-the-condition-of-an-existing-action-tp7593475p7593477.html Sent from the wix-users mailing list archive

Re: [WiX-users] How to install on a subfolder ?

-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-install-on-a-subfolder-tp7592965p7592967.h

Re: [WiX-users] Getting current downloading package name in BA for Web installer

when the bundle is started and cached(different than package cache), it creates a BootstrapperApplicationData.xml in the cached folder. You can parse this based on the PackageID to get the DisplayName. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.c

Re: [WiX-users] Burn Bundle Uninstall Questions

1) Remove the Registry Key in the ARP Uninstall Registry location for the productcode for the old bundle. 2) The active(upgrade) bundle is coded to execute the old(cached) bundle with the -quiet -uninstall flags. Your upgrade bundle should contain the final contents. Current: A.msi, B.msi Desired

Re: [WiX-users] Is this a Bug in Wix Bootstrapper command line?

Hi! If you're using TestBA written by bryan, you'll have to manually interpret your parameters. You'll have to implement what the BA will do when these are passed. The results you see from your other post is correct. Since you don't have the implementation, it won't run the uninstall. Go somew

[WiX-users] Wix Burn Built-In Variables

Hi All, We were trying to pass the [WixBundleVersion] on to an MSI from Burn: However, when the MSI ran, the commandline showed: Command Line: MSIFASTINSTALL=7 BUNDLE.VERSION=0.0.0.0 It passed 0.0.0.0 instead of our Bundle/@Version Value. Does anybody else see this behavior? Thanks! Richard

Re: [WiX-users] Burn and ExePackage

Thanks Tom. It is the expected behavior for the prereqs for the bootstrapper. But I was thinking it might be related to my issue. Maybe that the ExePackage(my ELO Monitor installation) is returning something to the engine that tells it to create another UI instance. I am still doing some tests.

Re: [WiX-users] Burn and ExePackage

Thanks for the quick reply! I initially thought that as well. But this was done on a clean image. A similar behavior that I noticed is when it installed a prerequisite for the BootstrapperApplication. Starting with a machine that doesn't have .net 4.5: The wixstaba loads and displays that .net i

[WiX-users] Burn and ExePackage

Hey all! I'm trying to step through the code during bundle installation, but seem to be stuck. I have a package that is installing with an ExePackage. At the end of a successful execution(onExecutePackageComplete), it will create a new instance of my bootstrapper UI(written in wpf/mvvmlight). I