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
My custom BA installs .NET 4.5.2 as a prerequisite. This works fine under most circumstances, but when the App is already installed and .NET has been uninstalled manually afterwards, further attempts to execute the same custom BA show the NET prereq dialog without any buttons.
Relevant extracts from the log:
[0AB4:06A4][2015-07-01T16:55:00]i001: Burn v3.10.0.1823, Windows v6.1 (Build 7601: Service Pack 1), path: X:\Setup.exe
[0AB4:06A4][2015-07-01T16:55:01]i000: Loading prerequisite bootstrapper application because managed host could not be loaded, error: 0x80070490.
[0AB4:06A4][2015-07-01T16:55:01]i101: Detected package: NetFx452Redist, state: Absent, cached: Complete
[0AB4:06A4][2015-07-01T16:55:01]i101: Detected package: ProgramFiles, state: Present, cached: None
[0AB4:06A4][2015-07-01T16:55:01]i104: Detected package: ProgramFiles, feature: ProductFeature, state: Local
[0AB4:06A4][2015-07-01T16:55:01]i199: Detect complete, result: 0x0
[0AB4:06A4][2015-07-01T16:55:47]i500: Shutting down, exit code: 0x642
Screenshot of dialog:
Curiously the uninstall from the Control Panel works, showing the prereq dialog correctly and it executes the .NET Framework installer that still exists in the Package Cache.
Originally opened by js69
The text was updated successfully, but these errors were encountered:
My custom BA installs .NET 4.5.2 as a prerequisite. This works fine under most circumstances, but when the App is already installed and .NET has been uninstalled manually afterwards, further attempts to execute the same custom BA show the NET prereq dialog without any buttons.
Relevant extracts from the log:
Screenshot of dialog:
Curiously the uninstall from the Control Panel works, showing the prereq dialog correctly and it executes the .NET Framework installer that still exists in the Package Cache.
The text was updated successfully, but these errors were encountered: