I’ve just started my first attempt at plugin development. I notice that the examples are all using Visual Studio 2005. That’s fine, but it’s more than a decade later; are there any examples that use modern development tools?
For example, I’m using VS2015, and when I try to open the “Visual Studio .NET 2005 Example” project, I get a bunch of warnings and errors.
[quote=302253:@Charles Weger]For example, I’m using VS2015, and when I try to open the “Visual Studio .NET 2005 Example” project, I get a bunch of warnings and errors.
Any suggestions are appreciated. Thanks.[/quote]
Hi Charles,
I wrote a book that has examples and some how-to information that uses visual studio 2013 community edition. The book table of contents can be viewed at http://scispec.ca and click on the books link. There are many resources available at http://Xojolibrary.com
Thanks for the links. I did get the plugin to compile, albeit with lots of warnings. Now I have to figure out how to link my existing C# code into the C++ environment, which looks like no picnic (but then I’m not primarily a Windows guy; maybe it’ll be easy).
I wrote a book that has examples and some how-to information that uses visual studio 2013 community edition. The book table of contents can be viewed at http://scispec.ca and click on the books link. There are many resources available at http://Xojolibrary.com[/quote]
Back in the old days there was a C++ version that was able to compile and create plugins for Windows, OSX, and Linux. Each operating system now requires its own C++ compiler. It would be much easier if there was only one compiler needed (kind of like a Xojo for C++), but I am not aware of any newer compiler that can cross compile and create a plugin.
Well… I’ve heard or read somewhere that Xojo is working on a way to build plugins within Xojo. I don’t know where I’ve read it though… But it would sure be a nice add on
Yes, I have heard this too. Although I am not sure what it will look like, or how it would work, I am excited for Xojo with this increased functionality.
My guess would be, some kind of way to export a Class. Now you can export it as Xojo Code. Or you can encrypt it. I think a third way of exporting a class (or module) would be something like “Save as Plugin”.