This project has moved. For the latest updates, please go here.
2
Vote

Dependencies are not found when loaded after plugin construction

description

When a dependency for a plugin is found at runtime and loaded on demand, VST.NET does not know the plugin's directory anymore - for this has been cleared so not to interfere with subsequent plugin loads.

The AssemblyLoader's PrivateProbePaths - which contains the plugin path - are cleared by the interop (VSTPluginMainInternal) when the initial loading is done.

The base path of the requesting assembly, which is present in the AssemblyResolve event arguments, will be used to load subsequent assemlby dependencies.

comments