we are glad @rui_mac you were able to solve your problem.
I'd just like to quickly recap to make this also clear for future readers.
Visual Studio has two "concepts" two organize your development work.
- Projects, which is basically a set of files plus a bunch of configuration options and instructions for the tool chain (compiler, linker,...) to build a binary (in our case here always a plugin library).
- Solutions, which are collections of above projects plus some additional global configuration data and more important, information on dependencies of the contained projects.
Now, our project tool can and does create both projects (for your plugins and for our frameworks) and a solution containing all of the above (actual workflow described in our docs under the links provided by Riccardo earlier on in this thread). So when you open such a solution and build your plugin project, also the frameworks it's depending on should be built.So, this is the way to go (project tool -> solution and projects -> open solution in Visual Studio).
But if you instead open just one of the generated projects directly, Visual Studio will implicitly generate a solution for you, but it still lacks the framework projects and the build of the opened project will fail (error: unresolved symbols, i.e. function or class names normally provided by our frameworks and used in the plugins code can not be resolved).
I hope this makes it a bit easier to understand.