I've been having a lot of trouble getting this to work the way I'd like and I was hoping someone could point me in the right direction.
I've got a custom managed BA that is pretty bare bones and chains a .NET prerequisite and my product's MSI. I'm specifying MsiPackage/@DisplayInternalUI="yes" and using a combination of custom and off-the-shelf dialogs to collect all the installation details I need. This works great for installations but the MSI UI is suppressed whenever I try to run the BA once the product is already installed. Whichever mode I try to initiate, and whether from the command line or Programs and Features, the MSI UI seems to be shut down, presumably by msiengine.cpp:MsiEngineCalculateInstallUiLevel, which 'suppresses internal UI during uninstall to mimic ARP and "msiexec /x" behavior'. Although I'm curious why the function enforces that behavior in the first place, I'd really just like to know how I'm supposed take advantage of the MSI's UI during repairs or changes. From the customers' perspective, running the installer a second time doesn't do anything when they should be seeing the change/repair/uninstall dialog that works fine when I run it from the MSI. Thanks in advance for any assistance, and I'd also like to thank you all for the help you've given me with my previous questions. Jacob Baughman ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
