I want to write a plugin for a software that will not be licensed with GPL.
However as this plugin needs to communicate with OPC, I wanted to use the .net standard OPC stack. This 'program' is licensed with GPL V2.
My question is whether my plugin which is a new C# Assembly can use the GPL licensed DLLs while not affecting the main program's license. (The plugin itself can be distributed with GPL V2 if needed to, but we would not prefer that)
The main application would load the DLL and use the data it gets from there (unknowing which DLLs it really uses and without access to those GPL licensed DLLs)
I already found this in the GNU FAQ, but I'm not sure if this is a clear case and I can continue to implement this way, or if I should organize a professional to check it.
EDIT: Sorry if my question was not clear but confusing to you. -The main application should be non-GPL and it will load the plugin dll which in turn loads the GPL dll. My question is if the main application is now influenced by this. It may be possible to have the plugin dll GPL also but not the main application. The main application will resolve the plugin dll with dependency injection and therefor the plugin will reference some core dll that holds interfaces for that.