New Post: Customizing the MSI User Interface NOT the Deployment UI

Hi Tom,
I've done as you mention. And, I do not see any change in the UI.

You've edited the copy of GenericBizTalkMSI.wxs in your deployment project folder to replace
<UIRef Id="WixUI_InstallDir" /> with <UIRef Id="WixUI_Mondo" />, removed <Property Id="WIXUI_INSTALLDIR" Value="INSTALLDIR" />,
and you don't see any change in the UI?

I do not see a change in the UI. I'm going to include the details of what I did below, including the generated candle and light commands.

In my btdfproj file, I added this line to force usage of my custom WXS file:

<WixProjectFile>Vancity.Isl.RequestResponse.wxs</WixProjectFile>

In my custom wxf file: (Vancity.Isl.RequestResponse.wxs) I changed the following:

<Feature Id="Complete" Title="$(var.ProductName) Setup" Description="All features installed." Display="expand" Level="1">
      <Feature Id="Program" Title="!(loc.ProductName)" Description="Program components." Level="1" Absent="disallow">
        <ComponentGroupRef Id="RedistComponentGroup" />
      </Feature >
      <Feature Id="Cleanup" Title ="Cleanup" Description="Testing" Level="3">
        <ComponentRef Id="Cleanup" />
      </Feature>
    </Feature>

    <!--<Feature Id="DefaultFeature" Level="1">
      <ComponentGroupRef Id="RedistComponentGroup" />
      <ComponentRef Id="Cleanup" />
    </Feature>-->

    <!--<Property Id="WIXUI_INSTALLDIR" Value="INSTALLDIR" />-->

    <UI Id="MyUI">
      <!--<UIRef Id="WixUI_InstallDir" />-->
      <UIRef Id="WixUI_Mondo"/>

      <Publish Dialog="ExitDialog"
          Control="Finish"
          Event="DoAction"
          Value="LaunchApplication">WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed</Publish>
    </UI>

The candle command was:

"C:\Program Files (x86)\WiX Toolset v3.7\bin\\candle.exe" "-dredist_folder=obj\Debug\redist" "-dProductUpgradeCode=8b3631db-cdb0-41f4-9418-2ad52476d423" "-dProductName=Vancity.Isl.RequestResponse" "-dProductId=638cfe30-5702-4eca-a174-903c4c306502" "-dProductVersion=1.0.0" "-dProjectVersion=1.0.0" "-dManufacturer=Vancity" "-dPackageDescription=Isl Request-Response Core" "-dPackageComments=Contains functionality to implement the ISL Request-Response integration pattern." "-dDeploymentTest=" "-dBizTalkAppName=Vancity.Isl.ESB" "-dProjectFilename=Vancity.Isl.RequestResponse.Deployment.btdfproj" -dIncludeDeployRulesShortcut=false -dIncludeSSOEditorShortcut=false -dCreateStartMenuShortcuts=True -out "obj\Debug\\" "Vancity.Isl.RequestResponse.wxs" "obj\Debug\RedistComponentGroup.wxs"

The light command was:

"C:\Program Files (x86)\WiX Toolset v3.7\bin\\light.exe" "obj\Debug\GenericBizTalkMSI.wixobj" "obj\Debug\RedistComponentGroup.wixobj" -out "C:\TeamFoundation\Vancity\ISL\RequestResponse\DEV\Main-Integration\Vancity.Isl.RequestResponse.Deployment\bin\Debug\\Vancity.Isl.RequestResponse-1.0.0.msi" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixUIExtension.dll" -ext "C:\Program Files (x86)\WiX Toolset v3.7\bin\\WixNetFxExtension.dll" -spdb

AND.... Just as I'm creating this I notice that the linker is referencing the obj\Debug\GenericBizTalkMSI.wixobj file instead of the renamed file obj\Debug\Vancity.Isl.RequestResponse.wixobj

Dean.

PS. I'll revert my custom name to the standard name and see if that fixes the problem.