Re: [WiX-users] Burn:GetCommandLineArgs

Thanks -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-GetCommandLineArgs-tp7597351p7597360.html Sent from the wix-users mailing list archive at Nabble.com. -- Compre

[WiX-users] Conditional config edit not writing node attributes

I'm using the WixUtilExtension, and specifically XmlFile, to conditionally configure a list of items that eventually appear in a GUI combo box. I have several check boxes on an installer dialog and when each is checked (true) I want to write to an element into a configeration file. Initially th

Re: [WiX-users] Burn:GetCommandLineArgs

The -? and -h are passed to your BA in the Command object that represents the command-line. No need to go parse the whole command-line yourself. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Origina

Re: [WiX-users] Burn:GetCommandLineArgs

Thanks for the resource. I found that I can use Environment.GetCommandLineArgs to get the -? switch. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-GetCommandLineArgs-tp7597351p7597354.html Sent from the wix-users mailing list archive at Nab

Re: [WiX-users] SECREPAIR: CryptAcquireContext: Could not create the default key container

Installing KB3000988 should fix this now. >Neil, > >I have the identical problem on Server 2012. >The offending patch is KB2984005 which installs a companion KB2977174. > >My MSI error log is exactly the same as yours. > >My workaround is: >Skip installation of KB2984005 and KB2918614. > >If remo

Re: [WiX-users] Shortcut creation seems to cause sxs assembly error in Event Viewer

We have some advertises and some that are not. I'll have to check if the apps to the shortcuts that are advertised are the only ones that produce sxs in the event viewer during installs. If so then I'll check to see what happens if I turn advertisement off. Thanks. -- View this message in conte

[WiX-users] Burn:GetCommandLineArgs

I have noticed that when I use -?, -h, or -help with my mba bundle, these parameters are stripped by Burn prior to returning Bootstrapper.Command.GetCommandLineArgs(). Yet using these switches with burn.exe or with my bundle.exe does not result in displaying a list of the built-in command line swi

[WiX-users] Burn / MsiProperty / Repair mode

Hello, I have a bundle with a slightly customized UI ( see http://stackoverflow.com/questions/12323106/customising-the-wix-burn-theme-with-additional-inputs ) to display an Editbox, and passing the value as a MsiProperty to an underlying MsiFile. In the Theme file : ... And in the bundle.w

Re: [WiX-users] Wix Upgrade Issue

You could also split your optional features into separate MSIs and use Burn to control their installation behaviour, which may be easier in the long run than trying to fight what windows installer is intended to do. You would probably need a custom BA though. -Original Message- From:

[WiX-users] Wix Upgrade Issue

HI, I never implemented this my self but try to do the following: 1. Use Minor upgrade instead of Major upgrade. (by definition Major upgrade is completely new installation that installs everything from scratch allowing to uninstall old versions and therefore when you choose particular features onl