Following on from my previous articles about ‘Passing multiple parameters to an ICommand in WPF’ and ‘Speeding up large WPF ComboBoxes’ the application stack I am currently working on has provided another article on a WPF subject!

The ability to show or hide UI elements based on criteria related to other elements is nothing new; only showing an ‘Other Details’ text box when a drop-down value of ‘Other’ is selected is the bread and butter of many end-user applications. There are a number of ways of doing this in the WPF/XAML/MVVM world, the default is often the use of a property on the ViewModel relating to the visibility (or enabled state) of the UI element in question, and this is how I have been implementing it until now!

The most recent set of screens I have been working on are a lot more complicated than other parts of the application (lots of business logic fields which depend on the values of other fields). Adding lots and lots of ‘IsEnabled’ or ‘IsVisible’ properties (along with their backing fields, and INotifyProperyChanged code) seemed very messy to me, and I felt there must be a better solution. I already use an IValueConverter to convert simple boolean values (FirstNameIsVisible for example) into WPF Visibility values, so I thought I could take that one step further and perform comparisons.


A simple binding to a property on your ViewModel or in the case of this example to a property on a selected dropdown list entry grants you the source for the comparison.

<GroupBox Header="Team Details" Margin="0,6,0,0"
  Visibility="{Binding ElementName=comboStaffMember, Path=SelectedItem.EmployeeType, 
	Converter={StaticResource ComparisonToVisibleConverter}, ConverterParameter='Manager||SeniorManager||GroupLeader'}">

The converter in the above code snippet is where all the magic happens; it takes the bound value and the ConverterParameter to perform the comparisons and return a Visibility value.

ValueConversion(typeof(bool), typeof(Visibility))]
public class ComparisonToVisibleConverter : IValueConverter {
	#region interface implementations

	public object Convert(object value, Type targetType, object parameter, CultureInfo culture) {
		try {
			string inputParameter = parameter?.ToString() ?? "";

			IEnumerable<string> paramList = inputParameter.Contains("||") ? inputParameter.Split(new[] {"||"}, StringSplitOptions.None) : new[] {inputParameter};

			return paramList.Any(param => string.Equals(value?.ToString(), param)) ? Visibility.Visible : Visibility.Collapsed;
		} catch {
			return Visibility.Visible;

	public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture) {
		return value?.ToString() != Visibility.Collapsed.ToString();

To allow for an ‘in’ style of comparison the CommandParameter is a string that can if required to contain a double pipe (‘   ’) as a separator. The parameter is taken and compared against the bound property (value in the above code). As a catch-all, the converter returns Visible in the case of a failure.

To reference the converter in your XAML code you need to declare it somewhere globaly or in resources local to your view.

<converters:ComparisonToVisibleConverter x:Key="ComparisonToVisibleConverter" />

This pattern provides for a quick, clean, and easy way to determine a UI Elements visibility based on the value of another element (or a computed value in the ViewModel).

Thank you to Daniil Kuželev for providing the header image for this article for free on Unsplash.