You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need DisplayInternalUI as I am having some extra dialogs in the .msi-file which are mandatory for the setup.
If the application is not running in an upgrade scenario everything is working fine, whereas a running application while upgrading brings the bootstrapper and the .msi-file into a not responding state.
The output of the log:
[2A34:28F0][2015-07-21T16:38:40]i001: Burn v3.10.0.1726, Windows v6.1
(Build 7601: Service Pack 1), path: W:\work\SETUP.exe ...
My fix (#408) was merged to Wix3 by @rseanhall. Currently we don't have FileInUse functional for WixStdBA in Wix4. So probably this issue can be closed.
I am using WiX Toolset v3.10.0.1726
I have a .msi-file that gets bundled within a bootstrapper.
MSI Defintion:
If executing the .msi-file directly,
FilesInUse
dialog shows up correctly if the application is running. Everything is working fine.Now I've integrated the .msi-file in a bootstrapper:
I need
DisplayInternalUI
as I am having some extra dialogs in the .msi-file which are mandatory for the setup.If the application is not running in an upgrade scenario everything is working fine, whereas a running application while upgrading brings the bootstrapper and the .msi-file into a not responding state.
The output of the log:
And the output of the msi-log (at least the last relevant lines):
So, why does the msi in the bootstrapped scenario hang (and causes the bootstrapper to hang either), and how do I fix this?
The text was updated successfully, but these errors were encountered: