Sent QuickOPC 2020.2 alpha version link + evaluation license by email.

We will take over the whole current state of UA-.NET-Legacy into QuickOPC 2020.2.

I had a somewhat deeper look into this.

There seem to be at least two changes made to address github.com/OPCFoundation/UA-.NET-Legacy/issues/1 .

The first is github.com/OPCFoundation/UA-.NET-Legacy/commit/552f5c2d8eed8df3eb34d1d00edafa82884e2707 . We already have this one in QuickOPC, because we are using the 1.03.342 release.

The second is github.com/AlinMoldovean/UA-.NET/commit/29208043d338c967537615419367f81b48d78231 .We do not have this second one in QuickOPC currently (it is not part of any release on GitHub yet).

Are you saying that to fix your problem, you need the second one too?

Regards

We might take over the modified OPC Foundation code for the upcoming QuickOPC version (2020.2). Tentatively, it may be released in 2-4 weeks, but do not take it as a promise. If your problem is truly caused by that issue in the UA stack, and it has been fixed on GitHub, it should go away.

Nobody has a support contract with us, we do not offer that. We have "upgrade assurance", which allow cost-effective access to newly released versions, but that is unrelated to support. The way we do support is that we support everybody to maximum reasonable/viable extent, but we provide no guaranteed support.

If you do not have upgrade assurance covering the date of us releasing the new version, you will need to purchase a version upgrade in order to use it.

Regards

You cannot do that.

You have purchased a product of ours, which includes some 3rd party libraries. This is also the case of certain OPC Foundation libraries you are referring to.
We are signing them with our key (they came unsigned by OPC Foundation), because strong-named assemblies (which is a requirement by many customers) of QuickOPC can only reference strong-named assemblies as well.

As a side note, of course we would not be willing to provide any support if what you are using was not what we have assembled as a product.

If there is a need to change something, it'll have to be done by us.

Very importantly though, there are also various licensing restrictions. It is complicated, but here are some (simplified) that you need to be aware of (in my understanding, IANAL):
- If we, as OPC Foundation Members, make a change to the code of those libraries, we need to provide that change back to OPC Foundation (RCL license). That would not be technically impossible, but we have a policy that we do not make such changes if at all avoidable.
- You (I suppose you are not an OPC Foundation Members) cannot use the UA stack source code that you get from OPC Foundation in your product without making source code of your product, and any modified libraries, public (GPL). See opcfoundation.org/license-agreement/ .

Regards

You are not supposed to do this.