Rob Mensching-7 wrote > > The wixstdba isn't designed to show the internal MSI UI. You'll probably > want to make a custom BA that is designed to show the internal MSI UI. >
Could you provide more detail about this? My simple test case sets DisplayInternalUI="yes" for my MSI package that is based on WixUI_Minimal. It works as expected when I install. It does give an unexpected "resuming the wizard" screen when I repair the bundle instead of showing the usual Repair screens. Uninstalling is completely quiet after I click Remove. I would say that wixstdba is supporting DisplayInternalUI significantly if not completely. So far, I've been thinking that my MSI's should be self-contained for UI and that the bundle should be used for prerequisites and chaining installs. I intended to use DisplayInternalUI for most of my MSI's. This would allow me to use a standard bootstrapper based on wixstdba for all my installs. I get the impression from what you are saying here and in other posts that you are leaning towards MSI's without UI with a custom bootstrapper providing the UI and passing values as properties to the MSI's. Is this what you intend? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-MsiPackage-and-DisplayInternalUI-tp7484106p7579167.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
