Our OPC UA client part consists of 1) the OPC UA .NET Stack and (parts of) client library from OPC Foundation, and 2) our own high-level classes on top of it.

Our own classes wouldn't probably be be so much of a problem - even if they don't work right away on other .NET implementations, it should be relatively easy to resolve it. But, as far as I know, the OPC UA .NET Stack has some dependencies on things that do not exist on Mono; as to the .NET Core, this is fairly new and I haven't heard about anybody trying. What precisely these problematic dependencies are, I do not know; I can guess that it has to do with WCF, and some crypto functions.

Best regards

Dear Sir,

it is correct that there is no need for COM/DCOM in OPC UA, and in corresponding part of our QuickOPC product.

The certification we have is for compliance with OPC UA standards, it is not related to the development/operating technology such as .NET.

Unfortunately, we currently do not support Mono or .NET Core. We also have no fixed plans to support them, although the decision will be re-evaluated from time to time.

Best regards

From: OPC Labs Contact Form - J.
Sent: Friday, May 15, 2015 10:33 PM
To: Zbynek Zahradnik
Subject: OPC Labs Contact Form - .NET certified - Linux

[...]

Hello,

I am currently researching OPC connectivity software, SDKs and toolkits and came across QuickOPC - it sounds all very good and interesting! I wonder though, since it is fully .NET certified (I understand, no need for COM/DCOM) - would it also work on Linux, e.g. using Mono or MS open source .NET core on Github?

www.mono-project.com/

github.com/dotnet/corefx

techcrunch.com/2015/04/29/microsoft-launches-its-net-distribution-for-linux-and-mac/

Thank you!