Support for Plugins running in separate AssemblyLoadContext with their own versions of Avalonia assemblies

[simonegli8]

Support for Plugins

In order to support plugins, each plugin should be able to run it's own version of Avalonia in a separate AssemblyLoadContext. Currently this is impossible, and one has to share the Avalonia assemblies between plugins and all plugins must use the same version of Avalonia. Maybe in order to implement this, one would need a common assembly defining basic interfaces of the things a plugin needs to be able to do, like opening a window or dialog.

[maxkatz6]

Have you checked UnloadableAssemblyLoadContext dev sample we have here? ALC containing Avalonia should be unloadable in full.

[simonegli8]

The sample still shares common assembly of Avalonia.Controls from default ALC. What I need would be a completely separate version of Avalonia in a separate ALC, so the plugin and the main app can use different versions of Avalonia without problems. Then the plugin would also have it's own event handler and resource lookup.