Creating a single MSI with multiple master binding files is going to be the easiest path.
One binding file will just be the "default" and the other an add-on.
First, add the new master binding XML next to your existing one. Then add this code to your .btdfproj to copy the extra bindings file into the MSI:
<!-- Force MSBuild to expand the item spec into physical file specs -->
<Output TaskParameter="Include" ItemName="ExtraBindingsSourceGroup" />
<Copy DestinationFolder="$(RedistDir)\Deployment" SourceFiles="@(ExtraBindingsSourceGroup)"/>
Next, modify your InstallWizard.xml to
include another wizard page
(another SetEnvUIConfigItem element) that collects the
of the additional bindings file. It cannot be the full path, only the file name. The EnvironmentVarName value must be
The net effect is that on a server deployment there will be a new page in the wizard to ask for the master bindings file name, and that file name will be routed into the deployment process via the MSBuild command line when the script is launched. That
be enough to do what you're asking.