WPF : Build Fault-Tolerant Composite Applications in .Net 6

[HansBuenting]

There is an article in MSDN magazine regarding a plugin structure in WPF (see link 1). The source code is based on .Net 4.5 and can probably easily be ported to 4.8. But how can all of this be implemented in .Net 6? Will it be possible to have a single Ui made up of different plugins with different versions of a dll? I know that there is now the AssemblyLoadContext to ensure separation of dlls. But how are user controls from the plugins embedded in the host application? In .Net 4.8 the following class is responsible for this (see link 2). I found a few more links (link 3, 4 and 5) that address the issue.

I got an answer that WPF currently has some issues when running with multiple AssemblyLoadContexts. Is there something new? Any best practices?

1.) https://docs.microsoft.com/en-us/archive/msdn-magazine/2014/january/wpf-build-fault-tolerant-composite-applications

2.) https://docs.microsoft.com/en-us/dotnet/api/system.addin.pipeline.frameworkelementadapters.viewtocontractadapter?view=netframework-4.8

3.) dotnet/runtime#16708 (comment)

4.) #1700

5.) https://stackoverflow.com/questions/66012470/system-addin-support-issue-while-migrating-wpf-a-composite-applications-to-net