All geek questions in one place

Using Burn as an Alternative to WiX Dialogs and Custom Actions

When transcoding into BootstrapperApplication (BA) methods and events, I implemented OnExecuteMsiMessage , and I was able to see the messages returned by my MSI during the installation. It also includes ActionData with other information.

Questions:

  • Is it possible to use Burn user interface dialogs instead of the user interface defined in our MSI (mainly WiX)?
  • Can we call our methods written in BA "during MSI installation"? Idea is to write custom actions as part of the BA and invoke them during the MSI installation.

I know that now we can write managed user actions, but just in case there is an opportunity to write methods in BA instead of user actions and call them the same way we plan to configure actions in MSI.

What should I do?

+4
source share
1 answer

Two quick answers:

  • Yes. In fact, this is the expected behavior. Bundles are designed to create a seamless installation. Providing a single user interface in your BootstrapperApplication is part of this.

  • No. BA does not work in an elevated manner, so it cannot change the state of the machine. If you are changing a machine, it must be part of the transaction in MSI. The BA should only be responsible for interacting with the user (aka: accept input, show progress, etc.).

+5
source

Source: https://habr.com/ru/post/1480988/

More articles:


All Articles