I just started working on an installer my company is creating and we are using WiX. During installation, we ask for the installer's name and email address. The "Next" button is disabled until both of those fields are no longer empty. However, the button doesn't become enabled until focus is changed from the last field edited. I would like to enable the button as soon as both fields have something in them. Here's what I've got so far:
<Control Id="Next" Type="PushButton" X="236" Y="243" Width="56" Height="17" Default="yes" Text="!(loc.WixUINext)">
<Condition Action="disable"><![CDATA[UNAME = "" OR EMAIL = ""]]></Condition>
<Condition Action="enable"><![CDATA[UNAME <> "" AND EMAIL <> ""]]></Condition>
</Control>
Any and all help will be greatly appreciated. Thank you.
This is not supported by Windows Installer. Control conditions are not evaluated as you type in an edit box.
A solution would be a dummy Validate button next to your edit box. The user can click it after typing in the edit box so the focus is changed and control conditions evaluated.
Another solution would be to use an external UI which evaluates control conditions as you type. Some commercial setup authoring tools have this feature built-in.
Related
Wix newbie - but I expect that is apparent.
I am using a modified version of the WixUI FeatureTree extension for an application that basically just copies files to specific directories. The installation wants to copy or remove based on a checkbox selection.
I have a feature for each installation package. I'm creating properties for each option and using them as a condition for each feature, changing the feature level to 1 or 0.
<!--Features for REVIT v2020-->
<Feature Id="Product2020" Title="Performance Seating v2020" Level="1">
<Condition Level="1">
<![CDATA[REVIT2020SELECTED = "Selected"]]>
</Condition>
<Condition Level="0">
<![CDATA[REVIT2020SELECTED <> "Selected"]]>
</Condition>
<!--Reference to Components.wxs component list hard coded-->
<ComponentGroupRef Id="2020Components" />
</Feature>
In the UI, I set the state of the property at the checkbox.
<Control Id="cbRevit2020"
Type="CheckBox"
Property="REVIT2020SELECTED"
X="50"
Y="110"
Height="10"
Width="150"
CheckBoxValue="Selected"
Text="Revit 2020"/>
The installation runs as expected on first run - features are installed based on the checkbox selection. Uninstall also works fine. Modify, however, does nothing regardless of checkbox state. I haven't changed anything in the FeatureTree.wxs custom file other than referencing my custom CustomizeDlg file.
I found reference to the issue (I think) here - https://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern/ However, it's over 10 years old and seems overly complex for what I need to do.
Does someone have a better approach?
BTW - yes, I know this is solvable simply by using the FeatureTree element. This is purely a personal preference, as I'm not a fan of that user interface in this application.
Thank you for any assistance.
Issue solved after quite a bit of searching and am posting in case it helps anyone else.
This article describes my desire and offers a good description of what is going on. https://www.joyofsetup.com/2007/05/30/feature-conditions-and-ui/
I removed the condition from the feature and moved it into the dialog as a publish event under the Next button control.
<Control Id="Next" Type="PushButton" X="248" Y="243" Width="56" Height="17" Default="yes" Text="!(loc.WixUINext)">
<Subscribe Event="SelectionNoItems" Attribute="Enabled" />
<Publish Event="AddLocal" Value="ALL">1</Publish>
<Publish Event="Remove" Value="PRODUCT2020">NOT REVIT2020SELECTED</Publish>
<Publish Event="Remove" Value="PRODUCT2021">NOT REVIT2021SELECTED</Publish>
<Publish Event="Remove" Value="PRODUCT2022">NOT REVIT2022SELECTED</Publish>
<Publish Event="Remove" Value="PRODUCTFAMILIES">NOT FAMILIESSELECTED</Publish>
I preset selections in the dialog based on install condition.
<SetProperty Id="REVIT2020SELECTED"
After="MigrateFeatureStates"
Value="Selected">
<![CDATA[REVIT2020INSTALLED AND (NOT Installed OR NOT !PRODUCT2020=2)]]>
</SetProperty>
I construct installer with custom dialogs and want to set action for the Next button to go to the directory selection dialog. So I use this code:
<Control Id="Next" Type="PushButton" X="236" Y="243" Width="56" Height="17" Default="yes" Text="[ButtonText_Next]">
<Publish Event="NewDialog" Value="InstallDirDlg">1</Publish>
</Control>
But the InstallDirDlg dialog is unknown here because I don't include WixUI_InstallDir schema.
So can I include it somehow or I should find the InstallDirDlg source and copy it to my .wxs?
(I try to modify the samples code SampleCustomUI7.wxs from the WiX tutorial).
I think you should refer to documentation, it has exactly this example in chapter "Customizing Built-in WixUI Dialog Sets", based on your "WixUI_InstallDir" UI type:
Inserting a custom dialog into a built-in dialog set
i am trying to make an installer. Thw checkBox and button i have added has a white background.
how can i get rid of those white spaces?
<Control Id="DesktopShortcutCheckBox" Type="CheckBox" X="80" Y="200" Width="290" Height="17" Property="INSTALLDESKTOPSHORTCUT"
CheckBoxValue="1" Text="Create a shortcut for this program on the desktop." />
<Control Id="Back" Type="PushButton" Text="Back" X="215" Y="243" Width="60" Height="17">
<Publish Event="NewDialog" Value="SecondDlg" />
</Control>
thnx
Unfortunately, the Windows Installer UI does not support transparent checkboxes. You have a few options:
Move the checkbox to a location that doesn't cover the background. For example, it is common to have a background in the install dialog, then a horizontal line at the bottom of the image then the buttons below the horizontal line. Putting the checkbox below the line with buttons looks good (looks standard) and can use the standard background color.
Make the checkbox control only as big as the checkbox itself then place static text next to the checkbox control with transparent background. This works but it means users must click the checkbox directly. Also, accelerator keys won't work which is an accessibility no-no. But it does look better.
Use an external UI handler to custom draw all your controls. This is easier with Burn in WiX v3.6+. The wixstdba UI can be customized using an XML "theme file". You can get a lot more custom UI than the standard Windows Installer UI supports.
It's all tradeoffs. Pick the one that works best for you.
I want to display a list of features that are going to be installed in the windows installer. This list will appear just before the user is about to install the product. I would like to know if there is a standard way to do this using WiX?
I tried to create a separate UI dialog just before the Verify Ready dialog which has a text control. The intention here is to display a text if a feature is being installed and hide that text if it is not being installed.
<Control Id="FeatureText" Type="Text" Text="SomeText">
<Condition Action="show">
<![CDATA[(&feature="3")]]>
</Condition>
<Condition Action="hide">
<![CDATA[(&feature="2")]]>
</Condition>
</Control>
the problem with this code is that the Action specified in the condition is not being performed.
After trying out a number of things I found that:
i- There is no need for quotes around the numbers and
ii- The controls can be set to hidden by default.
The following code is now working for me
<Control Id="FeatureText" Type="Text" Text="SomeText" Hidden="yes">
<Condition Action="show">
<![CDATA[(&feature=3)]]>
</Condition>
</Control>
but what I still don't know is, if this is the best/right way to do what I intend to do...
I have a modified FilesInUse dialog. Just including it in project and changing reference in UI does not help - I get "ICE20: Standard Dialog: 'FilesInUse' not found in Dialog table" error when building installation project.
Browsing the Net I've found one advice - to supress ICE validation for ICE20. Well, building the project with such settings works fine, and the msi also works fine, but I'm not sure that's a good solution to the problem.
Another advice was to modify FilesInUse and remove WixUIExtension from references, but as far as I know this way I'll end up with copying all the needed dialog files to my project. This I'd like to avoid.
So, what can be done to include my custom FilesInUse in WIX project correctly?
You could use a custom FilesInUse Dialog in the following manner:
<Fragment>
<UI>
<Dialog Id="FilesInUse" Width="370" Height="270" Title="Your product name">
<Control Id="Retry" Type="PushButton" X="304" Y ="243" Width="56" Height="17" Text="Retry" Default="yes" Cancel="yes">
<Publish Event="EndDialog" Value="Retry">1</Publish>
</Control>
<Control Id="Ignore" Type="PushButton" X="235" Y ="243" Width="56" Height="17" Text="Ignore">
<Publish Event="EndDialog" Value="Ignore">1</Publish>
</Control>
<Control Id="Exit" Type="PushButton" X="235" Y ="243" Width="56" Height="17" Text="Exit">
<Publish Event="EndDialog" Value="Exit">1</Publish>
</Control>
<Control Id ="InUseFiles" Type="ListBox" Width="300" Height="150" X="30" Y ="60" Property="FileInUseProcess" Sorted="yes" TabSkip="yes" />
</Dialog>
</UI>
</Fragment>
You just have to reference this Dialog into your Custom InstallDialog with the tag
<DialogRef Id="FilesInUse" />
All the tags mentioned are part of the ICE20 Dialog Requierements
Hope this helps. Have a nice day.
OK, I just spent some time trying to figure out how to solve this problem.
Though there are some good references in suggested thread, I think the FilesInUse dialog is a bit more specific to customize, so I decided to write a more concrete solution to the problem.
See, the problem is that MSI uses the FilesInUse dialog automatically, so if you try to change it somehow, you get errors such as FilesInUse not existing in Dialog table or duplicate FilesInUse dialog in table if you are referencing your custom dialog from other files.
The solution I found working was not to use DialogRef to Wix's FilesInUse dialog at all, but to make my custom dialog in main UI file (Where I would normally put DialogRef to FilesInUse) and name it FilesInUse.
Hope this helps other people having the same problem.
One more wrinkle is that the custom FilesInUse dialog will not be displayed when clicking Uninstall in Programs and Features since the uninstall is run with UILevel 3, so only the built-in FilesInUse will be displayed.
To work around that include this in your product.wxs:
<Property Id="ARPNOREMOVE" Value="1" />
Then when users press the Change (or Modify) button in Programs and Features, the Maintenance dialog will have a Remove button they can use to uninstall, and that will show custom dialogs. Products like Visual Studio only have a Change/Modify button.
One more thing is that Apps and Features (Windows 10) will disable the Modify button if the Uninstall key doesn't have a ModifyPath setting. It should be set to
MsiExec.exe /I{<yourproductcode>}
Your bootstrapper will need to do this. Not sure if the MSI can set it.
If building on the command line: light.exe -sice:ICE20...
If working in Visual Studio: Right click your setup project, select "Properties", Select "Tool settings" on left side of screen, Add "ICE20" to the "Suppress Specific ICE validation:" edit box.
See the related question and answers here: WiX replace dialog
User Yan Sklyarenko answered on Mar 25 '11:
Couple of articles to help you:
WiX
Tutorial
Neil Sleightholm's
article
You should find all the info you need for your case there.
User Bob Arnson answered on Mar 25 '11:
See "Changing the UI sequence of a built-in dialog set" in the topic
"Customizing Built-in WixUI Dialog Sets" in WiX.chm.