WIX MBA

Hi I would like to have information about creating a "Managed Bootstrapper Application" (Custom .NET UI) using the WiX?

With the arrival of the Windows Installer XML Toolkit (WiX) v3.5, another idea of fastened installer packs was included, and refined in v3.6. This conveyed two key components to the toolset:

The capacity to bunch a few individual Microsoft Installer (.msi) records together into a solitary installer executable and (alternatively) have them appear as just a single item in the Add/Remove Programs list

The choice to build up your own particular custom UI for the installer, incorporating one written in .NET

making an "Oversaw Bootstrapper Application" (Custom .NET UI) utilizing the WiX v3.6 SDK.

Quick Idea Review

The general thought is this: You have at least one "bundle" installer records (.msi or .exe) that you made or are from outsiders (ensure they have redistribution licenses). You need to enhance the establishment encounter for the end client, so you tie these installers into a solitary .exe which will introduce them in a foreordained request, alternatively permitting the client to choose which bundles and sub-components ought to be introduced. Take note of that the individual segment MSIs are introduced by means of "quiet" mode, so their UI won't be appeared (expecting they legitimately execute noiseless mode).

For instance: One should take Microsoft Office for instance. Office has a few individual items (Word, Outlook, Excel, and so forth) which, for this illustration, we'll expect are every individual MSI documents. Be that as it may, as an end client, I need to run a solitary installer, pick which items to introduce, consent to a solitary EULA, and have only one Add/Remove Programs passage. This can be accomplished by making a packaged installer that incorporates the majority of the individual item MSIs. Additionally take note of that Office has its own UI encounter, which varies from the run of the mill MSI ship dim UI.






What occurs at Runtime

At the point when the client executes your packaged installer, a WiX-gave local (ie: C++) application is at first stacked. This is the "Motor". This part of the installer is the thing that really connects with the Windows Installer APIs. The Engine does some underlying checks to ensure the adaptation of .NET required by our code has been introduced, and on the off chance that we've enlisted the .NET installer as a major aspect of our bundle chain, it will simply ahead and run that installer. When .NET is prepared, the WiX Engine stacks the class we've enlisted by means of the [assembly: BootstrapperApplication] get together property.

All correspondence with the Engine starting now and into the foreseeable future is done by means of the occasions accessible through the BootstrapperApplication base class.

__________________
Answered By StudyChaCha Member