Christian even your plugins are having the same effect. I tried JSONMBS & MemoryBlockMBS which I would presume are both console safe also are unable to be compiled.
I just created new project based on the Service template.
I added a line “dim j as new JSONMBS” and build it. Works here and I get the app build with MBS plugin in libs folder.
Yes my plugin loads, and as before, there’s no issue with my desktop app.
I’ve also confirmed that there must be something wrong with my plugin connected with console/service apps because when I moved my plugin out of the plugins folder and launched Xojo again, and created a new service app, your MBS plugins worked again.
I’m stumped. Why would my plugin work without issue in a desktop app but not a console/service app?
I wonder if anyone from Xojo can shed some light on this?
My custom plugin has a property which is a class from another plugin…Valentina. This particular class must be listed as not console safe because when I removed it from my module inside my plugin, no errors in my windows service app.
What particular circumstances would a class be definitely NOT console safe? I presume it’s anything to do with being GUI related.
I wasn’t using this property yet anyway so no workaround required.