Confused about the roll of burn (bootstrapper) vs the main msi installer
<p>I'm a bit confused about how wix burn and the main installer are expected to interact with each other.  I'm new to wix and windows installer technology in general.</p>

<p>Based on the examples I've seen I was under the impression the burn application would install prereqs then switch to the main installer.  However I've seen comments from searches that when using the burn application the main installer becomes secondary and the burn UI should be used instead.  This is reinforced by the behavior of the burn application. What I mean is the burn application has it's own license agreement, ARP entry, hides the main installer by default, and has it's own change/repair entry.</p>

<p>This has me confused because the burn application is lacking a lot of functionality the main installer has through MSI.  Some functionality I would consider essential such as feature selection, directory selection, and changing features.  But this is absent from the burn application.</p>

<p>I feel if I used the burn application as the primary I'd have to recreate the UI, while if I used the main installer for prereqs (if possible) I'd have to recreate the functionality burn provides.  Neither approach is desired, so I am wondering how other users of wix handle large projects.  Is it standard to write your own custom burn UI?  Any help that might clear up this confusion would be greatly appreciated.</p>