Creating an automatic data template fails, if the UI dispatcher changes

[flagbug]

I'm on WinRT and have created an app that is a share target

It seems like each time the app is opened as share target, it gets assigned a new UI dispatcher, while the AppDomain persists.

This is a problem, when creating the automatic DataTemplate at

ReactiveUI/ReactiveUI/Xaml/AutoDataTemplateBindingHook.cs

Line 26 in 3f725c8

public static Lazy<DataTemplate> DefaultItemTemplate = new Lazy<DataTemplate>(() => {

, since it's lazy and persists over the AppDomain and the first UI dispatcher gets cached in the DataTemplate.

When the dispatcher then changes, and the template with the old dispatcher is assigned to a control that was created on the new UI thread, line

ReactiveUI/ReactiveUI/Xaml/AutoDataTemplateBindingHook.cs

Line 67 in 3f725c8

itemsControl.ItemTemplate = DefaultItemTemplate.Value;

will result in a weird COM exception "COM object that has been separated from its underlying RCW cannot be used" (At least on WinRT)

[flagbug]

Maybe we can use https://msdn.microsoft.com/en-us/library/dd642243(v=vs.110).aspx here, so we get a new data template for each thread

[ChrisPulman]

Fixed in 19.4.1, XAML parser issue was located Uwp project has been retired fix is present in WinUI.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.