XAML parser resolving URIs (I get odd control behavior, and "The component 'XXX' does not have a resource identified by the URI" errors.

[wenbei421]

I am currently struggling with what I assume is this issue. I have a .NET 5.0 WPF plugin architecture and encounter errors if I have multiple plugins in different assembly load contexts. It seems to come down to issues with the XAML parser resolving URIs (I get odd control behavior, and "The component 'XXX' does not have a resource identified by the URI" errors.

Given that this is still an open issue, is there any known way to work around the problem? Thanks.

Originally posted by @mikeoliphant in #1700 (comment)

[ryalanms]

Hi, @wenbei421. We don't currently know of a workaround for assemblies of the same name in multiple AssemblyLoadContexts.