
Quote from DaviddeArgentina on February 12, 2023, 11:46 pmHello everyone,
I installed the Microsoft Visual Studio Community 2022 environment, with the purpose of trying to run the example program provided by the C# SDK to make plugins.
It wasn't easy for me to transcribe the VS 2015 readme with VS 2022. I finally got to a dll that I renamed as NBP, but VNW/Neobook doesn't recognize it as a usable plugin.
If someone is using this development environment, it would be extremely useful to generate some kind of instructions, to be able to follow the steps to make things work.
Hola a todos,
Instalé el entorno Microsoft Visual Studio Comunity 2022, con el propósito de intentar ejecutar el programa de ejemplo que provee la SDK de C# para hacer plugines
No me resultó facil de transcribir el readme de VS 2015 con VS 2022. Finalmente llegué a un dll que renombré como NBP, pero VNW / Neobook no lo reconoce como un plugin utilizable.
Si alguien está usando este entorno de desarrollo, sería de una enorme utilidad generar algun tipo de instructivo, para poder seguir los pasos para que las cosas funcionen.
Infinite thanks! / Infinitas gracias!
Hello everyone,
I installed the Microsoft Visual Studio Community 2022 environment, with the purpose of trying to run the example program provided by the C# SDK to make plugins.
It wasn't easy for me to transcribe the VS 2015 readme with VS 2022. I finally got to a dll that I renamed as NBP, but VNW/Neobook doesn't recognize it as a usable plugin.
If someone is using this development environment, it would be extremely useful to generate some kind of instructions, to be able to follow the steps to make things work.
Hola a todos,
Instalé el entorno Microsoft Visual Studio Comunity 2022, con el propósito de intentar ejecutar el programa de ejemplo que provee la SDK de C# para hacer plugines
No me resultó facil de transcribir el readme de VS 2015 con VS 2022. Finalmente llegué a un dll que renombré como NBP, pero VNW / Neobook no lo reconoce como un plugin utilizable.
Si alguien está usando este entorno de desarrollo, sería de una enorme utilidad generar algun tipo de instructivo, para poder seguir los pasos para que las cosas funcionen.
Infinite thanks! / Infinitas gracias!

Quote from Darbdenral on February 13, 2023, 1:16 am@daviddeargentina
Yes, because of my previous posts here asking for help with C# plugins and the lack of help/response from C# developers. I may be the only one currently using C# to create plugins. But I'm not a C# expert, I prefer Delphi. I've used Pascal/Delphi much longer, since Turbo Pascal 1.0 was released. ;)My intentions are to help with a release of a more complete SDK plugin template. But first, I wanted to figure out why the VisualNeoWin objects dialog will not work correctly in my C# projects, this is my very last step to a complete template. The current SDK falls short with example of edit actions. I did a very large plugin project with C#, the ezChrome plugin, anyone using it will see it's action interface is not polished as should be, reason being the object dialogs.
Anyways, my first thoughts are that you need to Select .NET Framework 4.5 at the top-left dropdown box of the Application tab and make sure the release platform is set to x86.. Unfortunately, the Robert Giesecke's Unmanaged Exports library is outdated and if I remember right, we're locked at .NET 4.5 because it's not updated. I use the latest stable 1.2.7 exports library/NET 4.5/x86 with no problems. I just followed the readme instructions closely. I don't remember any problems I might have faced updating to the Microsoft Visual Studio Community 2022 environment but it definitely works.
Here's a shortcut for having to rename your dll's. In your Build event tab, add to the post build event command this action, just change path as needed and compile when VisualNeoWin is not running. This was mentioned in the readme too.
copy $(TargetPath) C:\VisualNeoWin\Plugins\$(TargetName).nbpI hope this helps..
@daviddeargentina
Yes, because of my previous posts here asking for help with C# plugins and the lack of help/response from C# developers. I may be the only one currently using C# to create plugins. But I'm not a C# expert, I prefer Delphi. I've used Pascal/Delphi much longer, since Turbo Pascal 1.0 was released. ;)
My intentions are to help with a release of a more complete SDK plugin template. But first, I wanted to figure out why the VisualNeoWin objects dialog will not work correctly in my C# projects, this is my very last step to a complete template. The current SDK falls short with example of edit actions. I did a very large plugin project with C#, the ezChrome plugin, anyone using it will see it's action interface is not polished as should be, reason being the object dialogs.
Anyways, my first thoughts are that you need to Select .NET Framework 4.5 at the top-left dropdown box of the Application tab and make sure the release platform is set to x86.. Unfortunately, the Robert Giesecke's Unmanaged Exports library is outdated and if I remember right, we're locked at .NET 4.5 because it's not updated. I use the latest stable 1.2.7 exports library/NET 4.5/x86 with no problems. I just followed the readme instructions closely. I don't remember any problems I might have faced updating to the Microsoft Visual Studio Community 2022 environment but it definitely works.
Here's a shortcut for having to rename your dll's. In your Build event tab, add to the post build event command this action, just change path as needed and compile when VisualNeoWin is not running. This was mentioned in the readme too.
copy $(TargetPath) C:\VisualNeoWin\Plugins\$(TargetName).nbp
I hope this helps..