On 11 Jan 2013, at 22:16, "Hoover, Jacob" <jacob.hoo...@greenheck.com> wrote: > Yes, if you go with burn the desire is to not show any UI from any of the > installers. From what I understand, you have a feature tree in your MSI that > your users can change. In that case, you would need to write a BA to do the > feature tree and then pass in the options via a MsiProperty element. If the > number of features is small you could build a native BA based off of > WixStdBA, just injecting a new page with your options on it. WixStdBA is > however a bit complex for most, as it's written in C++ and it's UI isn't > using any existing libraries (to keep the BA small).
Thanks for this, it clears up a lot. Without having dug into writing burn UIs yet, how simple/difficult would it be to implement a simple check/message box - if .NET isn't installed, show a yes/no dialog asking if they'd like to install it, otherwise, if it is installed already, skip that step of the installation? If it's not too complicated, I can just do that, but I'd rather not throw away the entire power of the WiX UI stages, given the benefits (at the moment) seem to be minimal. Thanks, Nick ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
