Here you go. Just realized that since .NET Core an exe always has a corresponding dll file. So we can copy the dll files and can skip the exe files. In any case, we still need a dummy comment in the main patch of each plugin so we’re able to export the patch.
Attached you’ll find a
host.vl- this one would be the main application, loading the plugins from the “plugins” folder. In this example it will show a combo box to select the plugin which should run.interfaces.vl- this is the one file all others reference. It contains the plugin interface (calledIPluginin this example, which has anUpdateoperation returning a Skia layer)pluginA.vl- contains a classPluginAimplementingIPluginby rendering “Hello from A”pluginB.vl- contains a classPluginBimplementingIPluginby rendering “Hello from B”
You’ll have to export host.vl, pluginA.vl and pluginB.vl and manually copy the pluginA.dll and pluginB.dll files to a new plugins folder beside the host.exe. I also copied the *.dll.config and *.deps.json files, not sure they’re needed, but won’t hurt.
Tested with vvvv 5.2 and vvvv 6.0 preview (in the preview the string rendering in the dropdown is much nicer).
plugin-system.zip (15.1 KB)