4

While digging into BootstrapperApplication (BA) methods and events, I implemented OnExecuteMsiMessage, and I was able to see the messages being returned by my MSI during installation process. That also includes ActionData with some other information.

Questions:

  1. Can we use Burn's UI dialogs instead of the UI defined in our MSI (written mostly in WiX)?
  2. Can we call our methods written in BA "during MSI installation"? The idea behind this is to write custom actions as part of BA and call these during MSI installation.

I'm aware that we can write managed custom actions now, but just in case there are possibilities to write methods in BA instead of custom actions and call these similarly as we schedule custom actions in MSI.

What should I do?

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Farrukh Waheed
  • 2,163
  • 2
  • 29
  • 59

1 Answers1

5

Two quick answers:

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

  2. No. The BA does not run elevated so it cannot modify machine state. If you are changing the machine, it should be part of the transaction in an MSI. The BA should only be responsible for interacting with the user (aka: take input, show progress, etc).

Rob Mensching
  • 33,834
  • 5
  • 90
  • 130
  • so our Custom Actions scheduled for InstallExecuteSequence would reside in msi and those for InstallUISequence can be alternate with our BA methods?... I think to some extend (depending upon requirements) it is possible, right?... And we may not define WIX UI and using BA UI, so in MSI we would be left with InstallExecuteSequence... – Farrukh Waheed May 16 '13 at 07:22