Jul 27, 2010 at 3:21 AM
Edited Jul 27, 2010 at 3:24 AM
I'm trying to open a Vst Editor window in WPF. I've followed the steps in CorePlugin project Readme.txt to compile the EditorControl.Xaml but I don't have a clue how to use it. I've run into many hurdles trying to make something happen out of this project.
The code in Samples.CorePlugin uses the classes in Jacobi.Core.Plugin. The code in VstHost use the classes in Jacobi.Core.Host. Yet both projects
reference the same class names in different namespace, although VstHost seems complete and functional while CorePlugin seems empty and half-baked.
First I thought I needed to initialize EditorControl.Host but it uses IVstHostCommandStub of Core.Plugin which is not included in any examples, I can't initialize it with the Core.Host IVstHostCommandStub. PluginCommandStub in Samples.CorePlugin also seems
to be a re-implementation that does nothing else than logging. Is it useful for something? Finally, OpenFileSelector doesn't seem to do anything except logging, shouldn't it open/load a plugin?
If possible, could you please explain the steps needed to initialize/open EditorControl.xaml properly?
I've read in discussion that you don't want to include a wpf project in the source code because of the DotNet 3.5 framework dependencies but I think it wouldn't hurt. It's not like the 2.0 project compiles out of the box, removing the 3.5 project from the
solution shouldn't be too hard once you've figured out you need to remove missing assembly file references, remove code signing (because the key is not provided) and create/populate the '_sharedAssembly' folder in order to compile using 2.0 framework.
Anyway, if there is a working implementation in WPF somewhere else please tell me.