Are partial properties supposed to be able to marshal onto the UI thread?

[BrianDT]

When I read this: as they allow the CsWinRT generators to correctly produce the necessary WinRT marshalling code
From the page https://devblogs.microsoft.com/dotnet/announcing-the-dotnet-community-toolkit-840/
I assumed that they would.

However, if you don’t marshal the property changes manually then you get a COM exception. To me this makes the community toolkit generated property changes less useful than writing you own implementation that has in build handling of thread marshalling.

Example below confirms that community toolkit property changes are not marshalled.
Reproduced in:
https://github.com/BrianDT/CommunityToolkitMvvmMarshallingIssue

[Sergio0694]

This is completely expected, you're reading that paragraph wrong. "Marshalling" refers to "marshalling to native [Windows Runtime]", not "marshalling to the UI thread". You always have to do that yourself. I have a proposal to make this automatic in WinUI 3 but unfortunately it hasn't gone anywhere just yet.

[BrianDT]

Thank you for the clarification, I suspected that this might be the case, but I dared to hope.
Any proposal to build in "marshalling to the UI thread" certainly gets my vote.

[Sergio0694]

Here's the proposal: microsoft/microsoft-ui-xaml#2795 🙂