Separation of layers when implementing an MVVM C# ​​.NET application with plugins?

Question

Software design

Classic MVVM application. View, ViewModel, Model - we distribute it to different assemblies. For the View layer, we make projects aimed at different platforms (for example, WPF and Avalonia). It turns out everything is beautiful and convenient.
What if the application plans to use the plugin system? If the entire plugin is placed in one assembly, it turns out to be inconvenient, you need to create the same assembly for another platform. Interested in approaches to solving this issue, illustrative examples.