Hi Obi, that's alright, I'm suffering from the same problem, I only just saw that you'd replied.
Ok, yeah you're probably right, lets forget about the above issues that I was having in my little attempt to understand how things are all working. I can't find the code that I'd previously written to attempt to host a plugin using Vst.net so I just wrote a
very quick console app to try and replicate the problems I was having before:
static void Main(string args)
VstPluginContext context = OpenPlugin(@"C:\Users\james\Downloads\10Band_EQ\10 Band Graphic Eq v1.3.dll");
private static VstPluginContext OpenPlugin(string pluginPath)
HostCommandStub hostCmdStub = new HostCommandStub();
hostCmdStub.PluginCalled += new EventHandler<PluginCalledEventArgs>(HostCmdStub_PluginCalled);
VstPluginContext ctx = VstPluginContext.Create(pluginPath, hostCmdStub);
// add custom data to the context
// actually open the plugin itself
catch (Exception ex)
private static void HostCmdStub_PluginCalled(object sender, PluginCalledEventArgs e)
HostCommandStub hostCmdStub = (HostCommandStub)sender;
// can be null when called from inside the plugin main entry point.
if (hostCmdStub.PluginContext.PluginInfo != null)
Console.WriteLine("Plugin " + hostCmdStub.PluginContext.PluginInfo.PluginID + " called:" + e.Message);
Console.WriteLine("The loading Plugin called:" + e.Message);
This is really just me hacking a few of the bare essentials out of the sample host application, including a copy of the HostCommandStub class from the host sample.
With this I've tried loading in a few plugins, all of which throw an exception that the plugin failed to load, stemming from the VstUnmanagedPluginContext class when I try to actually create the plugin.
It's very possible that I'm doing something wrong, though, with the C#/C++ language split it's been very hard for me to debug and actually see what was causing the problems.