With great respect for Rob, and I agree that bal:Condition does not support a non-blocking warning today, however by adding a BAFunctions.dll to your StdWixBa bundle, you can implement c++ code to detect different conditions, and then use the information to log, display a string on a dialog, or block the setup, or change selections in the OnPlan handler.
I now use a mba and rarely create a WixStdBA with a BAFunctions.dll, so I am out of practice on the details, but looking at some old code, when I started working with wix almost two years ago, my bundle had some complex business rules where I needed to change which operatings systems and which editions of operatings systems I could support in the bundle depending on which "features" the user selected. Your general concept can be implemented using a BAFunctions.dll. There is a sample BAFunctions.dll in the wix source with example code at: src\burn\Samples\bafunctions There are other threads in this forum which provide more details on creating and using a BAFunctions.dll. Eventually I decided, for other reasons, to convert my projects to an mba, which provides a lot more flexibility than using the BAFunctions.DLL. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Warning-condition-in-Standard-BA-tp7600309p7600317.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
