Request that Burn respect setting MsiLogging (like it does MSIFASTINSTALL)

[wixbot]

I experimented with setting MsiLogging in Burn driven MSI packages, but found the results confusing. I was trying to use SetProperty to set MsiLogging (related to a remember property pattern for the VALUE_OF_MSILOGGING), however folks in this thread pointed out that doing this is not supported. Rob commented that a request that Burn respect MsiLogging like it does MSIFASTINSTALL was a reasonable request.

http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Use-of-MsiLogging-in-Burn-driven-MSI-td7597242.html

I was trying to provide 'testers' with a simple way to set the MsiLogging value on the command line of my mba bundle.exe (and pass that value in a property to the various msi packages.) (I also learned from MSDN that '_' should not be used so my mba converted myswitch=_v to MsiLogging='voicewarmup'.)

Originally opened by phogland

[vlsg]

Is there any way to up-vote this? We would very much like to be able to use MSILOGGING property.

[robmen]

This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution.

If you are interested in doing so yourself, our developer documentation provides a great checklist for getting started.

If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options.

[vlsg]

Thank you for the info Rob. I am new to this process so I appreciate the guidance you’ve provided below. :) -Vanessa From: Rob Mensching [mailto:notifications@github.com] Sent: Wednesday, January 31, 2018 1:47 PM To: wixtoolset/issues <issues@noreply.github.com> Cc: Vanessa Grimes <vgrimes@electrotek.com>; Comment <comment@noreply.github.com> Subject: Re: [wixtoolset/issues] Request that Burn respect setting MsiLogging (like it does MSIFASTINSTALL) (#4554) This issue is open and unassigned. That means it is waiting for someone to investigate the root problem, discuss possible solutions to that problem then implement the decided solution. If you are interested in doing so yourself, our developer documentation<http://wixtoolset.org/development/> provides a great checklist for getting started. If you are not interested then you are waiting for someone else to become interested. If this issue has been open for a long time then there probably isn't much interest in this particular issue. In that case, you'll want to consider how to motivate others to fix it for you. This is a pretty good list of support options<https://www.firegiant.com/support-options/>. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#4554 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AVknI_M9eusH0am88Hn7v6kn0eQsNlTBks5tQLUcgaJpZM4R0dL2>.

[chrpai]

I'm not sure Burn respects MSIFASTINSTALL. I was troubleshooting a RestartManager/Files In Use problem and noticed that Burn was passing MSIFASTINSTALL=7 to the MSI command line. When I added the property MSIFASTINSTALL and set it to 0 I could see the commandline contained both MSIFASTINSTALL=7 and MSIFASTINSTALL=0 In the log I could see it had the property and then I could see the property changed. I'm not sure MSI supports that and either way I'm still troubleshooting my issue.