如何让Caliburn.Micro的ComboBox显示对象ToString()返回值？

Great question! I’ve run into this exact frustration before—Caliburn.Micro’s default view-locating conventions can clash with WPF’s native ComboBox behavior when binding object collections. Let’s break down why this happens and how to fix it globally, so you don’t have to set DisplayMemberPath on every single ComboBox.

Why the "Cannot find view for..." Message Pops Up #

Caliburn.Micro is built to automatically resolve views for viewmodels out of the box. When you bind an object collection to a ComboBox, the framework treats each dropdown item as a potential viewmodel and tries to locate a matching view for it. If no view exists for that object type, you get that annoying error message instead of seeing the object’s ToString() output like you would in vanilla WPF.

Global Fix via Convention Manager #

The cleanest solution is to tweak Caliburn’s Convention Manager to override this behavior specifically for ComboBoxes. You’ll make this change in your Bootstrapper’s Configure method (the central place where you set up Caliburn’s core settings).

Option 1: Override ComboBox Element Convention #

This approach directly modifies how Caliburn handles ComboBox bindings, forcing it to fall back to native ToString() behavior when no DisplayMemberPath or ItemTemplate is explicitly set:

protected override void Configure()
{
    // Keep your existing Caliburn configuration here (e.g., container setup)

    // Customize ComboBox convention to restore native ToString() behavior
    ConventionManager.AddElementConvention<ComboBox>(
        ItemsControl.ItemsSourceProperty,
        "SelectedItem",
        "SelectionChanged")
        .ApplyBinding = (viewModelType, path, property, element, convention) =>
        {
            // Apply the default ItemsSource binding first
            ConventionManager.ApplyDefaultBinding(viewModelType, path, property, element, convention);
            
            var comboBox = (ComboBox)element;
            
            // Only intervene if no DisplayMemberPath or ItemTemplate is already set
            if (string.IsNullOrEmpty(comboBox.DisplayMemberPath) && comboBox.ItemTemplate == null)
            {
                // Create a minimal ItemTemplate that binds to the object itself (triggers ToString())
                var itemTemplate = new DataTemplate();
                var textBlockFactory = new FrameworkElementFactory(typeof(TextBlock));
                textBlockFactory.SetBinding(TextBlock.TextProperty, new Binding(".") { Converter = null });
                itemTemplate.VisualTree = textBlockFactory;
                
                comboBox.ItemTemplate = itemTemplate;
            }
        };
}

Option 2: Skip Item View Conventions for ComboBoxes #

If you prefer a more lightweight approach, you can tell Caliburn to skip applying item-level view conventions entirely for ComboBoxes:

protected override void Configure()
{
    // Existing configuration...

    // Override the default item convention logic
    var originalApplyItemConventions = ConventionManager.ApplyItemConventions;
    ConventionManager.ApplyItemConventions = (itemsControl, itemsSourceProperty) =>
    {
        // Don't apply item view conventions to ComboBoxes
        if (itemsControl is ComboBox)
            return;
        
        // Use the original logic for all other ItemsControls
        originalApplyItemConventions(itemsControl, itemsSourceProperty);
    };
}

How This Works #

• Option 1 explicitly sets a minimal ItemTemplate that binds to the object itself. WPF automatically converts this to the object’s ToString() result, bypassing Caliburn’s view lookup entirely.
• Option 2 prevents Caliburn from even attempting to resolve views for ComboBox items, letting WPF fall back to its native behavior.

Both approaches eliminate the need to set DisplayMemberPath on every ComboBox in your project, keeping your XAML clean and consistent.

内容的提问来源于stack exchange，提问作者Sabyasachi Mukherjee